Jump to content

Docker wont start


Brettv

Recommended Posts

Hi all,

I just updated to Beta 8, and now i cannot start docker. i had an existing image that i tried to use. Then even tried to create a new image and i get the following in my log

 

Sep 2 18:43:54 SERVO php: /etc/rc.d/rc.docker start

Sep 2 18:43:54 SERVO php: Maybe expand image file

Sep 2 18:43:55 SERVO php: Not starting Docker: mount error

Sep 2 18:43:55 SERVO php:

 

Any clues?

 

I just tried it in putty and add the following

 

root@SERVO:/etc/rc.d# rc.docker start

Maybe expand image file

mount: /dev/loop8 already mounted or /var/lib/docker busy

mount: according to mtab, /dev/loop8 is already mounted on /var/lib/docker

Not starting Docker: mount error

 

 

 

-Brett

Link to comment

Hi all,

I just updated to Beta 8, and now i cannot start docker. i had an existing image that i tried to use. Then even tried to create a new image and i get the following in my log

 

Sep 2 18:43:54 SERVO php: /etc/rc.d/rc.docker start

Sep 2 18:43:54 SERVO php: Maybe expand image file

Sep 2 18:43:55 SERVO php: Not starting Docker: mount error

Sep 2 18:43:55 SERVO php:

 

Any clues?

 

I just tried it in putty and add the following

 

root@SERVO:/etc/rc.d# rc.docker start

Maybe expand image file

mount: /dev/loop8 already mounted or /var/lib/docker busy

mount: according to mtab, /dev/loop8 is already mounted on /var/lib/docker

Not starting Docker: mount error

 

 

 

-Brett

 

I followed these instructions and everythign worked fien for me:

 

All seems to be working great, just re-downloading images now. Thanks!

 

I wasn't 100% sure of the update order but i did the following.

 

Deleted docker plg from plugins.

Updated unraid to beta8 & reboot

Ran btrfs subvolume delete

Started docker and added new img path

Ran  CP for existing template move

Deleted -boot/config/plugins/dockerMan.plg - /Docker-startup.plg  - /dockerMan-2014.08.28.tar.gz

Link to comment

I ended up manually running rc.docker stop, which after a minute seemed to kill docker,

then restarted docker via the web interface and it seemed to work fine.

 

Just strange as it happened right after a clean boot. The only other plugins i had running were sickbeard and subsonic

 

Will advise if it happens again, or i notice any pattern.

 

Thanks to those who read this thread

-Brett

Link to comment

Archived

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

×
×
  • Create New...