Closed Freshhat closed 1 year ago
Ok seems i figured out the issue, it's about time. The Firefox app itself needs about 30 min to start completley. Is there anything to improve this? With the last versions it took a few seconds only when i restarted the container
Is this issue seen every time the container starts?
Yep unfortunatley after every docker restart or even after a complete recreate via docker-compose. This happens also if i start with a fresh profile (removing the config volume and start with a empty one)
Also, on which system are you running the container ?
Also, on which system are you running the container ?
I'm running it on Fedora Server 35, running with docker version 20.10.22
I have the same problem. Do I need to wait for 30 minutes to start docker Standalone 20.10.17
I ran strace on the firefox process and found that it was wasting CPU and time trying to close a lot of file descriptors. Seems to be related to this issue: https://github.com/moby/moby/issues/44547
Specifying the ulimits for the container in my docker compose file solved the problem for me:
ulimits:
nofile:
soft: 65536
hard: 65536
I ran strace on the firefox process and found that it was wasting CPU and time trying to close a lot of file descriptors. Seems to be related to this issue: moby/moby#44547
Specifying the ulimits for the container in my docker compose file solved the problem for me:
ulimits: nofile: soft: 65536 hard: 65536
Thanks, this also solved it on my side. I can life with that option in my compose file. So from my perspective we can close this
Thanks for all the info. With the latest image, it should work without setting ulimits
in your compose file.
Currently i'm a little bit lost, after restarting the container i'm just getting a black screen. I can still see the cursor and also the clipboard menu, but nothing is loaded.
docker-compose:
docker logs output:
Screenshot WebApp:
Is there any other log, which i can provide?