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
I figured out that it is because we have too many files already and therefore this line takes a very very long time to run in scripts/start and scripts/start-celery as this
find /var/lib/docker/volumes/rodan_resources/_data ! -perm 0777 -exec ls -ld {} \;
And then we replace the original command section in production.yml with tail -f /dev/null.
After we launch the docker stack, we manually go into the container and comment out the line chmod -R a+rwx /rodan in /run/start or /run/start-celery and then execute.
We build docker images under tag fix_startscript which has commented out those two lines for production server.
We need to further discuss possible stable solutions for the future.
copied from #1241
I figured out that it is because we have too many files already and therefore this line takes a very very long time to run in
scripts/start
andscripts/start-celery
as thisRodan/scripts/start
Line 11 in 245db99
Currently we first run this on the NFS host
and then verify using
And then we replace the original command section in
production.yml
withtail -f /dev/null
.After we launch the docker stack, we manually go into the container and comment out the line
chmod -R a+rwx /rodan
in/run/start
or/run/start-celery
and then execute.We might need to rebuild all the images to remove the line. But we also need to make sure the permission status... Still thinking about the solution.
The text was updated successfully, but these errors were encountered: