Why do you have ~ here?
Also I see you have dockerproxy in there. Are you using Windows?
I personally keep all my files in my home folder in a folder named docker. Each container gets a subfolder with its name and docker-compose.yml file in it long with any folders that container may need to store data. So, in SWAGs case, I would have something like:
and I’d have this folder made:
and the docker-compose.yml file in the folder:
Have you ever had this running? If not, I’d copy my folder structure, and try running docker-compose up -d again and see what you get or anything different.
I’ve had issues with other containers using that /opt/ path incorrectly. I’d investigate that path first. Hope this is helping. Sounds like you’re really close. I’ve used SWAG in the past, but not with this dashboard. Also, you might want to add port 81:81 if you’re trying to access the dash locally. Might be helpful along the way. I saw you were missing that option when looking at the documentation. FWIW.
Its the same as you using . I have all my dockers under ~/opt which goes to my home ditectory.
Using Ubuntu Linux
Yes its working now, problem is sometimes it gets stuck when bringing down those mods during container recreation which then times out and gets those tar errors. I assume its bringing them down from github.
Thanks for all the suggestions. My problem boils down to downloading those specfic mods for some reason. It would be nice if they could be downloaded as images same as the swag image and it utilizes them rather than trying to download everytime swag container is created.