Jump to content

[SOLVED] Docker won't start in 6.0.1


roastdawgg

Recommended Posts

I just upgraded from 5.something to 6.0.1 and can't get Docker to start. I have gone into settings, Docker, and set the drop down to Yes, the size at 10GB, and the location at /mnt/cache/apps/docker/docker.img. I click apply and the page immediately reloads and docker isn't started and the form is back to default settings. I search the log and I see where it attempted to start Docker at boot, but there are no more log entries from the repeated times I have tried to start it.

 

Aug 21 20:10:21 unRAID emhttp: Starting Docker...

Aug 21 20:10:21 unRAID logger: /usr/bin/docker not enabled

Aug 21 20:10:21 unRAID rc.unRAID[4916]: Starting unRAID.

 

I can SSH in to the box and run docker commands from the command line...not that I know how to get it enabled from there.

 

Anyone have any idea why this won't start or what to do about it?

 

Thanks!

Link to comment

This sounds almost exactly like the problem I've been having. Main difference is that I seem to have a second problem piled on top of it, which is that when I click on the "Log" button in the webgui it just returns this error: "sh: /webGui/scripts/tail_log: No such file or directory" so I don't even have that to debug with.

What did you do to figure this out? I've tried changing the size of the docker image as well as sticking it in different spots, though I'm mainly just trying to stick it in /mnt/cache/docker.img

Also, anyone reading this know why I'm not seeing my logs?

Link to comment

Still no-go. I did what you suggested and as soon as I plugged it in to my Windows PC it did say that there were errors and repair them. However, upon booting up unRaid again I see no change from before. The log button still just pops up the same error (sh: /webGui/scripts/tail_log: No such file or directory) and trying to create a new docker image still does nothing as far as I can tell. I opened up the log from Tools>System Log and see the following lines at the end of it.

 

Aug 22 21:01:29 Tiriage emhttp: Starting Docker...

Aug 22 21:01:29 Tiriage logger: /usr/bin/docker not enabled

Aug 22 21:01:30 Tiriage avahi-daemon[1751]: Server startup complete. Host name is Tiriage.local. Local service cookie is 3994860686.

Aug 22 21:01:31 Tiriage avahi-daemon[1751]: Service "Tiriage" (/services/ssh.service) successfully established.

Aug 22 21:01:31 Tiriage avahi-daemon[1751]: Service "Tiriage" (/services/smb.service) successfully established.

Aug 22 21:01:31 Tiriage avahi-daemon[1751]: Service "Tiriage" (/services/sftp-ssh.service) successfully established.

Aug 22 21:04:01 Tiriage sshd[2156]: Accepted none for root from 192.168.0.101 port 61453 ssh2

Aug 22 21:04:12 Tiriage php: Deprecated absolute #command path: /plugins/dynamix.docker.manager/event/started

Aug 22 21:04:12 Tiriage php: /plugins/dynamix.docker.manager/event/started

Aug 22 21:05:30 Tiriage emhttp: /webGui/scripts/tail_log syslog 2>&1

Aug 22 21:09:40 Tiriage emhttp: /webGui/scripts/tail_log syslog 2>&1

 

Any more ideas out there about what's up?

Link to comment

Interesting, everything in the webGUI was still showing that I was running 6.0.1.

Anyway, definitely looks like something was corrupted/incomplete about the upgrade I ran. I wiped the drive and re-installed from a downloaded zip of 6.0.1 and all seems to be functional now. Thanks for the help!

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...