Container can not be accessed when run in a nested virtualised environment (Proxmon->Docker) #2619
-
Is there a pinned issue for this?
Is there an existing or similar issue/discussion for this?
Is there any comment in the documentation for this?
Is this related to a provider?
Are you using the latest release?
Have you tried using the dev branch latest?
Docker compose config usedversion: '3.3' Current BehaviorWeb interface of transmission can not be accessed from LAN. Expected BehaviorWeb interface should be accessible via server_ip:9091. How have you tried to solve the problem?I followed the "Debug your setup" wiki and it works as expected up until Accessing Transmission Web UI. Unfortunately, I could not find anyone with a similar issue elsewhere so I decided to ask here. Log outputStarting container with revision: 1103172 Transmission will run as User name: root Updating Transmission settings.json with values from env variables HW/SW Environment- OS: Proxmox 7-4.3
- Docker: 20.10.21 Anything else?I think the LOCAL_NETWORK= environment does not work properly. As you can see from the compose file, it is left on default 192.168.0.0\16. The client I am trying to access it is 192.168.0.60, which should be in the covered range. I would highly appreciate any help! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
This is a support question, not an issue. LOCAL_NETWORK does work properly, but you need to properly configure your networking. |
Beta Was this translation helpful? Give feedback.
This is a support question, not an issue. LOCAL_NETWORK does work properly, but you need to properly configure your networking.
Proxmox works perfectly fine as host with this setup.
I suggest choosing a subnet in class C such as /24 instead, /16 seems unnecessary large..
check your other proxmox network settings.
Are you using a CT or VM?