-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Container restart loop in Kubernetes #82
Comments
I am having the same identical problem when I try to deploy the docker-compose template using Portainer (on a NAS running OpenMediaVault) with Swarm mode enabled. |
Maintaining an application (answering questions, fixing bugs, adding new features...) is a hard and time consuming process. If you find this product useful and all the effort I put crafting this, I strongly encourage you to donation to help me being able to continue maintaining this and creating other great things on those platforms This issue seems related to #32. There is nothing I can do to fix this "issue". If you use multiple container for the same JDownloader, please make sure you're sharing its file so JDownloader knows update is done |
Not sure what you mean by "multiple container", I only have one replica running. If you could further elaborate what "its file" is, I can add a PV for it to keep it persistent. Maybe, the issue is this (at least I think so), @jaymoulin please tell me if I'm correct: Container is starting up. Jdownloader gets upgraded. Container restarts. At this point, in a normal Docker environment, the ephemeral storage of the container is beeing kept. Because a restart is not the same as a remove/redeploy. In Kubernetes, it's a redeployment which erases the ephemeral storage. So jdownloader gets updated again. Reading thought #32, I can imagine the issue could be fixed when adding a PV to /opt/JDownloader/. Correct? If so, could this cause other troubles? |
If Kubernetes redeploys the container, then your files are deleted. So, yes, you will result in an everlasting update process. |
@jaymoulin I tested it and you are right:
I may have a easy fix for that, let me check that first. If I'm right, expect a pull request ;-) |
Hi there
Used your container in docker-compose quite a while now. Worked great! Thanks, your work is highly appreciated.
I now tried to move it into Kubernetes. There, I've the following problem:
The container starts, tries to update jdownloader, shuts down, get restartet, and starts again trying to upgrade. It's like a upgrade loop. I haven't had that issue on pure docker-compose, so maybe something is wrong in what' I'm doing :-)
I added the container log at the end.
Setup: It's a single-node k3s Cluster on CentOS 7:
Kubernetes: v1.19.4+k3s1
Containerd: 1.4.1-k3s1
As the container starts and seems to work (except for the upgrade) I presume it's not an issue that my K3S is using Containerd instead of Docker. I assume the image is OCI compliant.
I have 2 PVs for config ans logs. I have a host bind mount for the download directory. Those are my environment vars:
XDG_DOWNLOAD_DIR=/opt/JDownloader/Downloads
TZ=Europe/Zurich
MYJD_USER=USERNAME
MYJD_PASSWORD=PASSWORD
MYJD_DEVICE_NAME=kubernetes
The text was updated successfully, but these errors were encountered: