Docker status stopped after upgrade to 6.3

[razr37]

Hello,

For some reason I cannot start docker after upgrade to 6.3.

First, I tried to Reboot Unraid in order to upgrade, system kept unmounting disks forever, I had to manually shutdown Unraid. I got a syslog before shuting down, see attached.

Fired back up unraid and now the "Docker" tab is there, but blank. I went to Settings/Docker stopped the docker, tried to start the docker, but it says Status: Stopped.

I even deleted the image file, re-enabled docker, with same result.

 

the log for docker shows:

Feb 6 09:52:01 Tower root: no image mounted at /var/lib/docker

Feb 6 09:52:01 Tower emhttp: shcmd (1312): umount /var/lib/docker |& logger

Feb 6 09:52:01 Tower root: umount: /var/lib/docker: not mounted

 

What should I do in order to get the docker started?

I attached both syslogs, one before stopping and the other one after starting with the new version.

I deleted some repetitive lines in order to bring down the size for attachment.

Thanks in advance.

 

syslog-2015-07-14.zip

syslog-2017-01-06_6.3.zip

[mgworek]

Did you reboot after deleting the image file? That happened a lot when i was doing the prerelease upgrades but rebooting after I delete the image file always fixed it.

[Squid]

You've got multiple drives with looks like bad connections.  I have a feeling the cache drive dropped offline.  Power down, reseat the cabling and any add on controllers, then try again.  Then post up your Diagnostics again if still having trouble.

[razr37]

the thing is that it is doing parity now bcs of the manual shutdown. Should I stop parity?

[Squid]

the thing is that it is doing parity now bcs of the manual shutdown. Should I stop parity?

Personally, I would because with the multiple drives all tossing what appears to be connection problems, a drive might get dropped during the parity check and then you've got another problem to deal with.

 

[trurl]

Then post up your Diagnostics again if still having trouble.

Not again, since he never posted anything but syslog to begin with.

 

razr37, you should always go to Tools - Diagnostics and post the complete diagnostics zip instead of just the syslog, unless specifically instructed to post a syslog.

 

the thing is that it is doing parity now bcs of the manual shutdown. Should I stop parity?

You should stop the parity check, shutdown and check connections, and then startup and check parity. And if parity check doesn't seem to be running well post diagnostics.

[Squid]

Then post up your Diagnostics again if still having trouble.

Not again, since he never posted anything but syslog to begin with.

Why do I have the feeling that this is going to be a "Pick On Squid" kinda day? 

[trurl]

Then post up your Diagnostics again if still having trouble.

Not again, since he never posted anything but syslog to begin with.

Why do I have the feeling that this is going to be a "Pick On Squid" kinda day? 

Didn't mean it that way. If anything I was picking on razr37.

[CHBMB]

Then post up your Diagnostics again if still having trouble.

Not again, since he never posted anything but syslog to begin with.

Why do I have the feeling that this is going to be a "Pick On Squid" kinda day? 

 

Did someone say "Pick on Squid Day"?  I'm down with that.... 

[Squid]

Then post up your Diagnostics again if still having trouble.

Not again, since he never posted anything but syslog to begin with.

Why do I have the feeling that this is going to be a "Pick On Squid" kinda day? 

 

Did someone say "Pick on Squid Day"?  I'm down with that.... 

Sounds like you should create a dedicated thread for that in lounge and see what kind of traction it gets

[razr37]

First of all, apologies, I thought syslog would do. So I disabled docker, just disabled bcs the option to remove the image is gone now, shut down unraid, reset the cables, turned back on, enabled docker, still get Status: Stopped. Started parity and it is running.

Tried to create docker.img in disk 4 and the result is the same.

tower-diagnostics-20170206-1208.zip

[Squid]

First of all, apologies, I thought syslog would do. So I disabled docker, just disabled bcs the option to remove the image is gone now, shut down unraid, reset the cables, turned back on, enabled docker, still get Status: Stopped. Started parity and it is running.

Tried to create docker.img in disk 4 and the result is the same.

The system is in a bit of a catch-22

 

What you've got to do is on the flash drive, edit the file config/docker.cfg

 

Change DOCKER_ENABLED="yes" to be "no"

 

Reboot the system

 

Go to settings - Docker, Hit Advanced, then Delete the image

 

Re-enable docker, and it should recreate the image.

 

Re-add your apps either via Add Container (the my* templates) or via the Apps tab and Previous Apps.  All of your appdata should be safe and the templates should already be filled out.  After the downloads, it should hopefully be all back to normal

 

[razr37]

Did the first two steps, but when I try to delete the image, there is no check mark where is supposed to be to delete the image.

See the screenshot

[razr37]

This one shows better what I mean

 

Did the first two steps, but when I try to delete the image, there is no check mark where is supposed to be to delete the image.

See the screenshot

[razr37]

On docker.cfg, see this line

DOCKER_APP_UNRAID_PATH=""

Is it missing the path?

see screenshot

[Squid]

On docker.cfg, see this line

DOCKER_APP_UNRAID_PATH=""

Is it missing the path?

see screenshot

The unRaid path doesn't matter...  You'll probably have to manually delete the docker.img file.  Swamped at work so hopefully trurl or others will pipe back in until I got more time  (hate bosses  )

[CHBMB]

On docker.cfg, see this line

DOCKER_APP_UNRAID_PATH=""

Is it missing the path?

see screenshot

 

Nope, it's normal.  Here's mine

 

DOCKER_ENABLED="yes"
DOCKER_IMAGE_FILE="/mnt/virtualisation/docker.img"
DOCKER_IMAGE_SIZE="20"
DOCKER_APP_CONFIG_PATH="/mnt/cache/.appdata/"
DOCKER_APP_UNRAID_PATH=""
DOCKER_OPTS="--storage-driver=btrfs"
DOCKER_AUTHORING_MODE="no"

[razr37]

Up and running. Went to flash/config and deleted the docker.cfg manually. Rebooted unraid, created a new image and it is running now. I am adding back my old containers now. Thank you all for your help.