Docker install failing #3795
-
Hello! I'm trying to install ospos via Docker. The system is Proxmox -> Debian 11 -> Docker with Portainer. I am totally new to Docker (and Debian and Proxmox), so please explain it like I'm 5! I tried the Dockerfile in Portainer without success. Then I tried via CLI and both fail in the same spot with the same error message. I wasn't sure if Portainer was the problem, but it doesn't seem to be. The error message is:
Any ideas as to what I'm doing wrong? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 5 replies
-
If you use proxmox isn't it Debain -> Proxmox -> Debian -> Docker with Portainer? It seems that you might be missing some directories for some reason. I would start from the docker compose instead. I have not worked with portainer so not sure how to run it through their UI. |
Beta Was this translation helpful? Give feedback.
-
Yes, you are quite correct - Debain -> Proxmox -> Debian -> Docker with Portainer. I'm wondering if something went wrong installing Docker so tonight I installed a Docker LCX via a script (a potentially unwise idea but hey, gotta learn somehow!) It seemed to go much smoother. Installing with the Dockerfile in Portainer resulted in the same error however. I then tried to pull an image from Docker Hub and that seems to have worked well. I cannot access anything on the ip of the container as it's set to something strange (172.x.x.x when my local network is 192.168.1.x), but I will continue to work on that. If I cannot get the IP address figured out, I will take a run at Docker compose and see if that will let me set an IP for the container. Thanks! |
Beta Was this translation helpful? Give feedback.
-
More progress. I've read up on Docker compose and Docker in general and I have found my main issue. It might help total Linux noobies like myself if the Docker install instructions looked more like this:
I had to learn how to download files from the web with the CLI. Then I downloaded the Dockerfile thinking it was going to download everything it needed, but I really needed to download the project zip file and start with that. That all said - I'm still not at a working install. My docker compose up seems to be frozen at: It's been there a solid 10 minutes. I've canceled (Control - C) the install and re-run docker compose up to see if it was a glitch, but it stops in exactly the same place. I went back to the Getting Started wiki page on install, it mentioned to run docker compose build before docker compose up, so I canceled and ran the build, then re-ran up and still stuck in the same spot. So I started looking at docker compose vs docker-compose. Went down a little rabbit hole. Installed docker-compose using a guide. Failed. Found another guide (https://cloudinfrastructureservices.co.uk/how-to-install-and-use-docker-compose-on-debian-11/) that worked and now docker-compose is installed so I'm golden right? Nope. Stuck in the same place! So that's where things are at for today. I'll continue to work on this as I feel like I'm making progress. I'm documenting this all here for future generations. Any suggestions will be greatly appreciated, thank you! |
Beta Was this translation helpful? Give feedback.
-
Success! I went back to the Docker compose (aka Portainer Stack) and inspected the network section carefully looking for differences between it and the Portainer container. I found that the "Port configuration" in the working Portainer container was "0.0.0.0:8000:8000" while the ospos port configuration was "127.0.0.1:80:80". I edited the ospos port configuration to "0.0.0.0:80:80" and re-started the stack and ospos came up immediately in my browser. Once I get a bit more familiar I will write up a quick Portainer specific guide and post it here. I think Portainer is a bit more accessible to noobies like me. |
Beta Was this translation helpful? Give feedback.
Success! I went back to the Docker compose (aka Portainer Stack) and inspected the network section carefully looking for differences between it and the Portainer container. I found that the "Port configuration" in the working Portainer container was "0.0.0.0:8000:8000" while the ospos port configuration was "127.0.0.1:80:80". I edited the ospos port configuration to "0.0.0.0:80:80" and re-started the stack and ospos came up immediately in my browser.
Once I get a bit more familiar I will write up a quick Portainer specific guide and post it here. I think Portainer is a bit more accessible to noobies like me.