This message was deleted.
# epinio
This message was deleted.
Hi Kelly, quick idea, is your cli same version as your server? (
epinio info
should tell you)
epinio info 255 (5.670s) < 135353 ✔️ Epinio Environment Platform: k3s Kubernetes Version: v1.22.9+k3s1 Epinio Server Version: v0.8.0 Epinio Client Version: v0.8.0
Hm this all look fine. I wish we printed the actual body of the response (that
part). You can still find the actual response I think if you increase the TRACE_LEVEL environment variable on the epinio-server deployment to
or more
let me send you some commands
kubectl edit deployment -n epinio epinio-server
• search for
• increase the value to
• save and exit • wait until the epinio server pod is recreated
then try the command again and check the epinio-server pod's logs
you should find more information on what went wrong
I had a look at the logs controller. One way to get a 400 Bad Request is if the app has no workload. And looking at your
epinio app list
output yours doesn't have one. I think that's the issue.
epinio app logs
gives you the logs of the running app (aka the workload). What you want is the staging logs so the command should be
epinio app logs --staging python-pip
and that should work. Of course, in any case, the command deserves a better error message. I will create an issue for this.
feel free to add more information if you want