You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Somewhere after version 8.1.8 the zeebe container is constantly restarting because it cannot access files in /usr/local/zeebe/data/ (.topology.meta in 8.4.0). I'm using the .env and Dockerfile from this repository. All other containers like different databases, kibana, keycloak, my own images, etc. run completely fine.
According to the official Dockerfile documentation:
If any build steps change the data within the volume after it has been declared, those changes will be discarded.
So you would have to move VOLUME declarations down after you create the directories and after the COPY instructions.
I also read somewhere that VOLUME would create an empty directory if it doesn't exist yet. In this case mkdir would fail and because you chain with && the chown and chmod would be ignored.
The text was updated successfully, but these errors were encountered:
@Chris-Maechler Thanks for reporting this.
Could you please provide more info about the versions? (e.g. OS, Docker daemon and CLI versions) and how to reproduce the issue.
Somewhere after version 8.1.8 the zeebe container is constantly restarting because it cannot access files in
/usr/local/zeebe/data/
(.topology.meta
in 8.4.0). I'm using the.env
andDockerfile
from this repository. All other containers like different databases, kibana, keycloak, my own images, etc. run completely fine.According to the official Dockerfile documentation:
So you would have to move
VOLUME
declarations down after you create the directories and after theCOPY
instructions.I also read somewhere that
VOLUME
would create an empty directory if it doesn't exist yet. In this casemkdir
would fail and because you chain with&&
thechown
andchmod
would be ignored.The text was updated successfully, but these errors were encountered: