Jake L.

Thanks @Djoss those steps appear to have fixed it. Was there anything I did wrong, or is this just something that happens from time to time? If needed, output.log was empty and error.log just had this line repeated: Missing chrome or resource URL: resource://gre/modules/UpdateListener.jsm

Thanks for the reply. Here's everything from docker logs Firefox after trying to start it again. It's not set to any tag so should be pulling the latest. [init ] container is starting... [cont-env ] loading container environment variables... [cont-env ] APP_NAME: loading... [cont-env ] APP_VERSION: loading... [cont-env ] DISPLAY: executing... [cont-env ] DISPLAY: terminated successfully. [cont-env ] DISPLAY: loading... [cont-env ] DOCKER_IMAGE_PLATFORM: loading... [cont-env ] DOCKER_IMAGE_VERSION: loading... [cont-env ] GTK_THEME: executing... [cont-env ] GTK_THEME: terminated successfully. [cont-env ] GTK_THEME: loading... [cont-env ] HOME: loading... [cont-env ] QT_STYLE_OVERRIDE: executing... [cont-env ] QT_STYLE_OVERRIDE: terminated successfully. [cont-env ] QT_STYLE_OVERRIDE: loading... [cont-env ] TAKE_CONFIG_OWNERSHIP: loading... [cont-env ] XDG_CACHE_HOME: loading... [cont-env ] XDG_CONFIG_HOME: loading... [cont-env ] XDG_DATA_HOME: loading... [cont-env ] XDG_RUNTIME_DIR: loading... [cont-env ] container environment variables initialized. [cont-secrets] loading container secrets... [cont-secrets] container secrets loaded. [cont-init ] executing container initialization scripts... [cont-init ] 10-certs.sh: executing... [cont-init ] 10-certs.sh: terminated successfully. [cont-init ] 10-check-app-niceness.sh: executing... [cont-init ] 10-check-app-niceness.sh: terminated successfully. [cont-init ] 10-cjk-font.sh: executing... [cont-init ] 10-cjk-font.sh: terminated successfully. [cont-init ] 10-clean-logmonitor-states.sh: executing... [cont-init ] 10-clean-logmonitor-states.sh: terminated successfully. [cont-init ] 10-clean-tmp-dir.sh: executing... [cont-init ] 10-clean-tmp-dir.sh: terminated successfully. [cont-init ] 10-fontconfig-cache-dir.sh: executing... [cont-init ] 10-fontconfig-cache-dir.sh: terminated successfully. [cont-init ] 10-init-users.sh: executing... [cont-init ] 10-init-users.sh: terminated successfully. [cont-init ] 10-jwm.sh: executing... [cont-init ] 10-jwm.sh: terminated successfully. [cont-init ] 10-nginx.sh: executing... [cont-init ] 10-nginx.sh: terminated successfully. [cont-init ] 10-vnc-password.sh: executing... [cont-init ] 10-vnc-password.sh: terminated successfully. [cont-init ] 10-web-data.sh: executing... [cont-init ] 10-web-data.sh: terminated successfully. [cont-init ] 10-x11-unix.sh: executing... [cont-init ] 10-x11-unix.sh: terminated successfully. [cont-init ] 10-xdg-runtime-dir.sh: executing... [cont-init ] 10-xdg-runtime-dir.sh: terminated successfully. [cont-init ] 15-install-pkgs.sh: executing... [cont-init ] 15-install-pkgs.sh: terminated successfully. [cont-init ] 55-check-snd.sh: executing... [cont-init ] 55-check-snd.sh: sound not supported: device /dev/snd not exposed to the container. [cont-init ] 55-check-snd.sh: terminated successfully. [cont-init ] 55-firefox.sh: executing... [cont-init ] 55-firefox.sh: terminated successfully. [cont-init ] 56-firefox-set-prefs-from-env.sh: executing... [cont-init ] 56-firefox-set-prefs-from-env.sh: terminated successfully. [cont-init ] 85-take-config-ownership.sh: executing... [cont-init ] 85-take-config-ownership.sh: terminated successfully. [cont-init ] 89-info.sh: executing... ╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮ │ │ │ Application: Firefox │ │ Application Version: 101.0.1-r0 │ │ Docker Image Version: 22.10.4 │ │ Docker Image Platform: linux/amd64 │ │ │ ╰――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╯ [cont-init ] 89-info.sh: terminated successfully. [cont-init ] all container initialization scripts executed. [init ] giving control to process supervisor. [supervisor ] loading services... [supervisor ] loading service 'default'... [supervisor ] loading service 'app'... [supervisor ] loading service 'gui'... [supervisor ] loading service 'certsmonitor'... [supervisor ] service 'certsmonitor' is disabled. [supervisor ] loading service 'jwm'... [supervisor ] loading service 'xvnc'... [supervisor ] loading service 'nginx'... [supervisor ] loading service 'logmonitor'... [supervisor ] all services loaded. [supervisor ] starting services... [supervisor ] starting service 'xvnc'... [xvnc ] Xvnc TigerVNC 1.12.0 - built Oct 23 2022 14:15:52 [xvnc ] Copyright (C) 1999-2021 TigerVNC Team and many others (see README.rst) [xvnc ] See https://www.tigervnc.org for information on TigerVNC. [xvnc ] Underlying X server release 12013000, The X.Org Foundation [xvnc ] Tue Oct 25 19:15:57 2022 [xvnc ] vncext: VNC extension running! [xvnc ] vncext: Listening for VNC connections on /tmp/vnc.sock (mode 0660) [xvnc ] vncext: Listening for VNC connections on all interface(s), port 5900 [xvnc ] vncext: created VNC server for screen 0 [supervisor ] starting service 'jwm'... [supervisor ] starting service 'nginx'... [nginx ] Listening for HTTP connections on port 5800. [supervisor ] starting service 'app'... [app ] Mozilla Firefox 101.0.1 [supervisor ] starting service 'logmonitor'... [logmonitor ] Monitoring log file: /config/log/firefox/error.log [logmonitor ] Monitoring status file: /tmp/.firefox_shm_check [logmonitor ] Monitoring status file: /tmp/.firefox_membarrier_check [supervisor ] all services started. [supervisor ] service 'app' exited (with status 0). [supervisor ] service 'app' exited, shutting down... [supervisor ] stopping service 'logmonitor'... [supervisor ] service 'logmonitor' exited (got signal SIGTERM). [supervisor ] stopping service 'nginx'... [supervisor ] service 'nginx' exited (with status 0). [supervisor ] stopping service 'jwm'... [supervisor ] service 'jwm' exited (with status 0). [supervisor ] stopping service 'xvnc'... [xvnc ] Tue Oct 25 19:16:00 2022 [xvnc ] ComparingUpdateTracker: 0 pixels in / 0 pixels out [xvnc ] ComparingUpdateTracker: (1:-nan ratio) [supervisor ] service 'xvnc' exited (with status 0). [finish ] executing container finish scripts... [finish ] all container finish scripts executed.

Just upgraded to the new version v22.10.4 and the container is unable to start. Container logs show: [logmonitor ] Monitoring log file: /config/log/firefox/error.log And viewing that I see this: Missing chrome or resource URL: resource://gre/modules/UpdateListener.jsm It was ok using the "latest" branch up until this update, but going back to the previous tag oddly still fails to boot. No changes on my side other than the update to the container but happy to test any suggestions. Thanks.

After a few hours of poking around on these forums and my system, I think I fixed it. For anyone else in a similar situation, I followed the excellent guide found here on deleting the docker.img file and re-creating it. https://forums.unraid.net/topic/36647-official-guide-restoring-your-docker-applications-in-a-new-image-file/ Apparently when I did that earlier something must have not worked (or I didn't fully complete it) but following the steps below solved it and I re-added all my containers without issue. I can only guess that my recent container updates must have affected the size as it was over the 70% threshold. This time when re-creating it I doubled it to 40Gb which should give me more breathing room.

Hi all. I normally have about a dozen or so running VMs, but since last night my Docker GUI has been unresponsive and the terminal drags to a crawl. I noticed this shortly after I updated my GluetunVPN container, which then set my dependent containers in a "rebuild" cycle. Currently, my other containers can run fine w/ access to them (Plex, Mealie, etc.) but I'm unable to do anything in the Docker GUI page as the Unraid (logo?) bars just keep bouncing up and down (hope that makes sense, lol). I've tried the following to troubleshoot it: - Restarted the host - Change to an older GluetunVPN tag (v3.26.0 from 2 months ago) - Stopped all the containers from running but left the docker daemon running - Deleted and reinstalled the "Docker vDisk location" docker.img file - Verified all my /mnt/user/appdata/ folders have available permissions for my users (they do, nothing appears changed) Doing any of the above has no effect on the GUI or console lag, and when I check the "top" I don't show anything really running more than 15 or so percent. The only thing I noticed is that prior to all of this I hit the 70% threshold in Docker memory usage as shown from the Dashboard. I've attached my diagnostics file in case it can be of help. This is really the first real problem I've hit that I haven't been able to figure out, so any insight would be greatly appreciated! *** I did just kick off an extended test in the "Fix Common Problems" section prior to running this diagnostics output, but that was not running prior to the issues above *** Thanks, Jacob ark-diagnostics-20220114-0913.zip