Closed typkrft closed 2 years ago
This may be an edge case, but I run containers through a VPN container. To do that I have to add the port to the VPN container. I believe however the VPN container is already using port 80 internally.
example
services: gluetun: image: qmcgaw/gluetun restart: unless-stopped container_name: gluetun cap_add: - NET_ADMIN devices: - /dev/net/tun:/dev/net/tun ports: - 8888:8888/tcp # HTTP proxy - 8388:8388/tcp # Shadowsocks - 8388:8388/udp # Shadowsocks # Port Mapping - 10036:80 # Openbooks volumes: - gluetun:/gluetun environment: # See https://github.com/qdm12/gluetun/wiki VPN_SERVICE_PROVIDER: redacted VPN_TYPE: openvpn OPENVPN_USER: redacted OPENVPN_PASSWORD: redacted SERVER_CITIES: redacted DOT: "off" OPENVPN_CIPHER: aes-128-cbc TZ: redacted dns: - redacted openbooks: container_name: openbooks image: evanbuss/openbooks:latest # environment: # BASE_PATH: /openbooks/ volumes: - books:/books/books # ports: # - '10036:80' command: --persist restart: unless-stopped network_mode: "service:gluetun" depends_on: - gluetun
This works I'm not sure what the issue was, maybe a caching issue.
This may be an edge case, but I run containers through a VPN container. To do that I have to add the port to the VPN container. I believe however the VPN container is already using port 80 internally.
example