August 23, 20178 yr Hi guys, I am running 6.3.5. I ran into an issue where I got a segfault while updating two docker containers (see below for one example). I was able to re-seat my ram and fix my issue, but as the docker container is deleted as a step before the run command it no longer showed on the unraid dashboard under dockers. Luckily I saved the errors, so I just had to get in the console and manually run the commands again and it populated back into the dashboard. It would be good if on error it either rolls back to the previous image or have it populate somehow in the dashboard so that it can run the run command again saving your settings. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="sabnzbd" --net="bridge" -e TZ="America/New_York" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -p 8080:8080/tcp -p 9090:9090/tcp -v "/mnt/user/appdata/downloads":"/downloads":rw -v "/mnt/user/appdata/apps/sabnzbd/incomplete-downloads":"/incomplete-downloads":rw -v "/mnt/user/appdata/apps/sabnzbd":"/config":rw linuxserver/sabnzbd unexpected fault address 0x1502b10 fatal error: fault [signal SIGSEGV: segmentation violation code=0x1 addr=0x1502b10 pc=0x93101d]
August 25, 20178 yr When you lose a docker from the dashboard, It's still listed as a template under the docker menu. You can go to the docker menu and select it from your known templates, simply deploying the docker again.
August 26, 20178 yr Author 7 hours ago, Tuftuf said: When you lose a docker from the dashboard, It's still listed as a template under the docker menu. You can go to the docker menu and select it from your known templates, simply deploying the docker again. Ok thanks! Still learning dockers
Archived
This topic is now archived and is closed to further replies.