May 10, 201511 yr EDIT: I had to manually create the folder. Thanks Squid. I am following the official guide and it said it'd take some time to make the image though did not give en estimate on how long. So far the "docker" option on the main bar has not shown up and I am curious how long it took everyone until theirs did. This is on a new Samsung 850 evo 500GB drive and is currently parity checking if it matters (yay 13+ day parity check). Thanks in advance to any help.
May 10, 201511 yr I am following the official guide and it said it'd take some time to make the image though did not give en estimate on how long. So far the "docker" option on the main bar has not shown up and I am curious how long it took everyone until theirs did. This is on a new Samsung 850 evo 500GB drive and is currently parity checking if it matters (yay 13+ day parity check). Thanks in advance to any help. What size did you enter for the image size?
May 10, 201511 yr Author I am following the official guide and it said it'd take some time to make the image though did not give en estimate on how long. So far the "docker" option on the main bar has not shown up and I am curious how long it took everyone until theirs did. This is on a new Samsung 850 evo 500GB drive and is currently parity checking if it matters (yay 13+ day parity check). Thanks in advance to any help. What size did you enter for the image size? The default that showed up: 10GB.
May 10, 201511 yr So /mnt/cache/docker.img ? If so, can you open your log and see if there is anything inside referencing docker?
May 10, 201511 yr Author So /mnt/cache/docker.img ? If so, can you open your log and see if there is anything inside referencing docker? Yes, exactly that path. Could it be I didn't make a user share yet? It's a fresh install since I got the last bits of my stuff in tonight. Below is every reference to docker. May 9 17:44:50 Tower logger: Starting docker.io May 9 17:44:50 Tower logger: /usr/bin/docker not enabled May 9 17:53:21 Tower php: /etc/rc.d/rc.docker start May 9 17:53:21 Tower php: Not starting Docker: new image file path doesn't exist May 9 17:56:50 Tower php: /etc/rc.d/rc.docker start May 9 17:56:50 Tower php: Not starting Docker: new image file path doesn't exist
May 10, 201511 yr Hmm, shouldn't matter about a user share. Do you actually have a cache drive assigned on the system?
May 10, 201511 yr Author Hmm, shouldn't matter about a user share. Do you actually have a cache drive assigned on the system? Yes. It's assigned and I can place files on it. It's showing green in the Main section.
May 10, 201511 yr Hmm, this is really odd. Can you go to the tools -> system log page and download a full log and share it here for review. I'm sure its just something simple that we are missing here.
May 10, 201511 yr Author Attached is the current system log. It seems I'm cursed with so many issues with unRaid when I've barely used it yet. syslog.txt
May 10, 201511 yr So /mnt/cache/docker.img ? If so, can you open your log and see if there is anything inside referencing docker? Yes, exactly that path. Could it be I didn't make a user share yet? It's a fresh install since I got the last bits of my stuff in tonight. I'm confused when you say you used that exact path, and yet didn't create a user share yet. If you didn't use that EXACT path, then the folder you specify for the docker.img file has to already exist.
May 10, 201511 yr Author So /mnt/cache/docker.img ? If so, can you open your log and see if there is anything inside referencing docker? Yes, exactly that path. Could it be I didn't make a user share yet? It's a fresh install since I got the last bits of my stuff in tonight. I'm confused when you say you used that exact path, and yet didn't create a user share yet. If you didn't use that EXACT path, then the folder you specify for the docker.img file has to already exist. Your previous suggestion fixed it. When I went to quote you I was unable to find your previous post; did you delete it seconds after posting?
May 10, 201511 yr So /mnt/cache/docker.img ? If so, can you open your log and see if there is anything inside referencing docker? Yes, exactly that path. Could it be I didn't make a user share yet? It's a fresh install since I got the last bits of my stuff in tonight. I'm confused when you say you used that exact path, and yet didn't create a user share yet. If you didn't use that EXACT path, then the folder you specify for the docker.img file has to already exist. Your previous suggestion fixed it. When I went to quote you I was unable to find your previous post; did you delete it seconds after posting? Yes.. I reread your message about exact path and then deleted it. Then I saw the discrepancy and recreated the post (worded differently)
May 12, 201511 yr /mnt/cache/docker.img is fine for the docker img location. It is not in a folder so won't be touched by mover. That's where mine is and I think is the recommended location, though others have done it differently. When you said you used the default size, did you then press the Apply button? I don't know if this has changed in recent betas, but there wasn't actually a default size, just an example size. Something has to be actually entered for the size.
May 12, 201511 yr Author /mnt/cache/docker.img is fine for the docker img location. It is not in a folder so won't be touched by mover. That's where mine is and I think is the recommended location, though others have done it differently. When you said you used the default size, did you then press the Apply button? I don't know if this has changed in recent betas, but there wasn't actually a default size, just an example size. Something has to be actually entered for the size. The issue has already been solved. I updated the title and my latest post with what I did to solve it as well. Thanks for the additional help, though.
May 12, 201511 yr /mnt/cache/docker.img is not in a folder so it's not clear what you did. What about the 13+ day parity check you mentioned? That is definitely not normal. Are you having a problem with that?
May 12, 201511 yr Author /mnt/cache/docker.img is not in a folder so it's not clear what you did. What about the 13+ day parity check you mentioned? That is definitely not normal. Are you having a problem with that? You can reference my first post to see what I did to fix the issue. On the first line it says I had to manually create the folder. As far as the parity check that ended up going faster and only took 12 hours. It apparently just took a little bit of time for the first half an hour or so. Again I already solved the issue which is why I marked the thread as [solved].
Archived
This topic is now archived and is closed to further replies.