dtempleton Posted September 3, 2014 Share Posted September 3, 2014 I have followed the threads about issues with getting Docker to start in beta 8. I had it running in beta 7 with gfjardim's dockerMan plugin. Following various threads, I removed all of the dockerMan plugin parts, and deleted the btrf subvolumes, eg: http://lime-technology.com/forum/index.php?topic=34980.0 and pducharmes' instruction for removing btrf subvolumes that I can't find now. Then I restarted in beta8. Then I installed the beta8 version of dockerMan. https://raw.githubusercontent.com/gfjardim/dockers/beta8/dockerMan/dockerMan.plg (I don't see dockerMan on the extension page) Trying to install the dockerMan again shows: /usr/local/sbin/plugin install https://raw.githubusercontent.com/gfjardim/dockers/beta8/dockerMan/dockerMan.plg 2>&1 2>&1 plugin: installing: https://raw.githubusercontent.com/gfjardim/dockers/beta8/dockerMan/dockerMan.plg plugin: not reinstalling same version pushing "start" on the Extentions:Docker page of the webgui does nothing, while running the equivalent /etc/rc.d/rc.docker in terminal gives this error: root@Tower:/etc/rc.d# rc.docker start Creating new image file for Docker: size: 4G fallocate: : open failed: No such file or directory Not starting Docker: failed to create image file Trying the Docker extension again the syslog shows a similar error: Sep 3 11:38:27 Tower php: /etc/rc.d/rc.docker start Sep 3 11:38:27 Tower php: Creating new image file for Docker: size: 4G Sep 3 11:38:27 Tower php: Not starting Docker: failed to create image file I have a btrfs cache drive (256G) that is (or was) the home of my docker install and apps, but I don't see how to specify that target now. Thanks for any help Link to comment
dmacias Posted September 3, 2014 Share Posted September 3, 2014 You don't have to install anything in beta8, just point it to a docker.img and select the size in GB's. All your dockers will be stored in that img file. Link to comment
jumperalex Posted September 3, 2014 Share Posted September 3, 2014 Wait what? So a single monolithic img? For all containers? Not one per container? Link to comment
reiteravi Posted September 3, 2014 Share Posted September 3, 2014 sorry 4 interrupting as i have the same problem: where is this docker.img file - non existeng on my system Link to comment
dtempleton Posted September 3, 2014 Author Share Posted September 3, 2014 sorry 4 interrupting as i have the same problem: where is this docker.img file - non existeng on my system Absolutely. The Docker Start page defaults to /mnt/disk1/docker.img but this doesn't exist and the path is greyed out in the field. Oh! I pointed this field to /mnt/cache/docker.img and it made a nice 4GB image for me, and Docker listed as 'started'. Lemme play with that for a bit. non-intuitive, I think. Link to comment
reiteravi Posted September 3, 2014 Share Posted September 3, 2014 i guessed so and tried it 1st but the greyed out field is not editable in my system turned out its my browser 's noscript that blocked me Link to comment
dtempleton Posted September 3, 2014 Author Share Posted September 3, 2014 Wait what? So a single monolithic img? For all containers? Not one per container? i guessed so and tried it 1st but the greyed out field is not editable in my system On mine it wasn't editable but you could type the correct path over it. Link to comment
megalodon Posted September 4, 2014 Share Posted September 4, 2014 Mod move to correct forum please, this is the v5 support forum. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.