Nokoff Posted July 25, 2014 Share Posted July 25, 2014 Hi I ran the fix permissions utility as suggested by someone on the forum (to be able to access these docker config files for editing from my windows pc) and it seem to have broken docker. The problem I'm having is that the docker containers will not start. I fire off docker start couchpotato and get this root@Tower:/mnt/cache/docker# docker start couchpotato couchpotato root@Tower:/mnt/cache/docker# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES root@Tower:/mnt/cache/docker# No containers active.. I believe its the permissions that is preventing me from starting them. Any advice appreciated. Quote Link to comment
nacat78 Posted July 25, 2014 Share Posted July 25, 2014 Have had the happen to me already, the only thing that fixed it was to remove containers/images and add them again. Quote Link to comment
pinion Posted July 25, 2014 Share Posted July 25, 2014 They might be starting and crashing too. Try to do docker -logs couchpotato and post the output. It might just be docker -log.... but I think it's logs. Quote Link to comment
JM2005 Posted July 25, 2014 Share Posted July 25, 2014 Have had the happen to me already, the only thing that fixed it was to remove containers/images and add them again. Same thing I had to do. Quote Link to comment
Nokoff Posted July 27, 2014 Author Share Posted July 27, 2014 Well this seems to be a real problem... I managed to fix as per your suggestion but I hope someone does something about the permissions script breaking the docker containers. Quote Link to comment
nacat78 Posted July 28, 2014 Share Posted July 28, 2014 Well this seems to be a real problem... I managed to fix as per your suggestion but I hope someone does something about the permissions script breaking the docker containers. I added this info to the Docker quick start thread and emailed jonp about this issue, they will be looking into it... Quote Link to comment
smdion Posted July 28, 2014 Share Posted July 28, 2014 Well this seems to be a real problem... I managed to fix as per your suggestion but I hope someone does something about the permissions script breaking the docker containers. I added this info to the Docker quick start thread and emailed jonp about this issue, they will be looking into it... Dang.. wish I saw this thread before... I just ran fixperms as well and had the same issue. Deleting and re-adding now.... Quote Link to comment
Neo_x Posted July 28, 2014 Share Posted July 28, 2014 lol same issue was having permissions issues to copy some files via SMB to the array, and thus clicked new permissions, after which it got stuck on the cache drive requiring a hard reset. anyhow long story short. thx for the advice guys - re-adding all the docker images now. just takes forever to download though Quote Link to comment
smdion Posted July 29, 2014 Share Posted July 29, 2014 I did some searching and it seems we can do newperms /mnt/user and it won't touch the cache drive Quote Link to comment
gfjardim Posted July 29, 2014 Share Posted July 29, 2014 I did some searching and it seems we can do newperms /mnt/user and it won't touch the cache drive The correct command is newperms /mnt/user0 Quote Link to comment
smdion Posted July 30, 2014 Share Posted July 30, 2014 I did some searching and it seems we can do newperms /mnt/user and it won't touch the cache drive The correct command is newperms /mnt/user0 Good clarification if you use the mover. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.