Unable to figure out why my container keeps getting a 172 address, can I borrow a second pair of eyes? #404
Unanswered
RiffyDivine
asked this question in
Ask for Help
Replies: 1 comment 1 reply
-
I use OMV which is Debian based, so I've not used Ubuntu (which I know is based on Debian). If I want my docker network to bridge to my main network, I have to create a docker bridge network. 1 other thought occurred to me, have you set 'Primary Hostname' from the settings menu? Just a thought, not trying how to suck eggs :) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
🛡️ Security Policy
📝 Describe your problem
Now I never had this issue before when I was using ubuntu but since moving to arch I am now having an issue with my arr stack all getting internal 172 network address over just bridging or hosting to the systems ip. So I pulled one from it and tested with that one as a new container and same issue. Can someone look at the compose file and let me know where my error is?
I am at a bit of a loss for where the issue is coming from. It is leading to issues since the link inside dockge is for my local ip and port, when setting them up it errors out cause they all want the internal ip address docker is giving them and it's just leading to issue.
version: "3.7"
services:
sabnzbd:
image: lscr.io/linuxserver/sabnzbd:latest
container_name: sabnzbd
environment:
- PUID=1000
- PGID=1000
- TZ=America/Chicago
volumes:
- /docker/appdata/sabnzbd/config:/config
- /incoming:/downloads #optional
- /incoming/incomplete:/incomplete-downloads #optional
ports:
- 8080:8080
restart: unless-stopped
networks: {}
📝 Error Message(s) or Log
No response
🐻 Dockge Version
1.4.2
💻 Operating System and Arch
arch
🌐 Browser
firefox
🐋 Docker Version
24.0.7
🟩 NodeJS Version
No response
Beta Was this translation helpful? Give feedback.
All reactions