Epinio is now available from the Civo Marketplace https://twitter.com/CivoCloud/status/1582008344004288512 https://www.civo.com/marketplace/Epinio

please like this tweet if you like epinio :D

Interesting read: https://thenewstack.io/what-we-learned-from-enabling-developer-self-service/

Good article!

Hi guys, I tried to push my local image with epinio. It show that kubelet can not pull image because it can’t find in docker.io registry. Does anyone know what is the cause of this problem ? Is it because I’m using Apple silicon while my image is Amd64 ? (Docker has this same issue i think) I’m using epinio push --container-image-url <my-image> as a push command.

With simple example projects e.g. paketo/samples epinio works wonderfully. When I go to my own projects the issues I have are build issues. Like this. Where do you recommend learning more about dealing with these issues?

Hi everyone, I just installed epinio on minikube using Helm in my macbook (M1)

helm install epinio --create-namespace --namespace epinio epinio/epinio --set global.domain=<http://192.168.49.2.sslip.io|192.168.49.2.sslip.io>

After doing a

minikube service -n epinio epinio-ui --url

, I’m able to access the Epinio UI via

<http://127.0.0.1:63777>

but the

admin/password

login is not working (see screenshot). Anyone know why? 🤔 Thanks in advance

While I like the pack builds is there a way to also bypass the build portion of epinio and use my own build if I want too?

It's the easiest way to begin moving legacy code into epinio

And I do test before hand to see if that app is available using a curl command

Part of testing this out for legacy apps is trying to see if I can export the helm chart so that I can move this from a dev to deploy scenario in CI

Hi @freezing-holiday-13112, could you export an higher

TRACE_LEVEL

env var to get some logs? In your shell for the cli, and in the epinio deployment for the server

Is there a way to have epinio just do a build?

ll

Hello, Can Epinio support promoting app across environments ? for example, dev and staging with different configmaps/secrets/namespace in the same Kubernetes cluster and production in another Kubernetes cluster ?

anybody tried running epinio on rancher desktop...(moby) via M1 Pro... the k3d seems to be crashing

Hi everyone! Just wanted to announce that we have just released the v1.8.0 🦋 https://github.com/epinio/epinio/releases

Hi all, new to epinio world ! I would like some help, after setting up my env and deploying sample app ( it worked ) I wanted to deploy a hello world flask python sample but I am getting the error message: " error pushing app to server: can't deploy app: Internal Server Error: release epinio-sampl-7d9397f28fdd55cee79fb62dd235433294384b7d failed, and has been uninstalled due to atomic being set: timed out waiting for the condition" Any hints in how to debug its root cause ?

I tried the same app deployment on docker and that just worked without any issues

is your port 8080 ?

You mean the container port ? No that's 8001

Hi @square-stone-81820, bt default Epinio is expecting the app to listen to the 8080 port, but with the latest version of Epinio you can specify a different one. So you can either change your app to listen to the 8080, or specify the 8001 with a custom chart value 😉

That's something I was looking for. Following the https://docs.epinio.io/tutorials/single-dev-workflow I would be able to run a simple python app right ?

Sure! You maybe will need to add a

Procfile

to your application

hmmm will look into that.. thank you!

I see documentation on scaling, but does epinio support auto-scaling out of the box?

Hi, I'm trying to create a custom service without specifying a helm chart. I'm planning to put all content in the values section. I can register the service successfully using kubectl apply, but when I try to "epinio service create ..." it complains about missing/wrong format URL for helm-chart. Is there a way to do this?

Hi guys! I’m trying to install Epinio on our experimental cluster. However, when installing I’m getting the following error:

Error: rendered manifests contain a resource that already exists. Unable to continue with install: ClusterIssuer "letsencrypt-production" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "<http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>": must be set to "Helm"; annotation validation error: missing key "<http://meta.helm.sh/release-name|meta.helm.sh/release-name>": must be set to "epinio"; annotation validation error: missing key "<http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>"

Any ideas what might be causing this?

I’m probably not reading the docs right or something. But I tried installing Epinio according the documentation. But what is the admin password to log in?

Things I noticed while exploring Epinio for the first time When creating a new Application, the UI will show a Failed error sometimes, but the build is continuing (not sure why though) When using the UI and creating a new application and the build fails, it is in a broken state. However when I try to edit the configuration to select a different commit the UI doesn’t have the old values. Also when I update the values I get an error that it can’t find the git tag. Exploring buildpacks for the first time Buildpacks install yarn with the

modules-folder

option which installs all the packages in a different directory than node_modules 😱 This is very non-standard, but figuring out how to get something working.