Bug: gluetun port tcp 8888 bind: already in use

[atticusmatticus]

Is this urgent?

Yes

Host OS

macOS

CPU arch

Apple Silicon

VPN service provider

ProtonVPN

What are you using to run the container

docker-compose

What is the version of Gluetun

Running version v3.39.1 built on 2024-09-29T18:16:23.495Z (commit 67ae5f5)

What's the problem 🤔

After latest Docker Desktop update (v4.35.0) my typical way of pulling and starting up containers after a reboot failed:
docker-compose pull; docker-compose up -d --remove-orphans;

gave the following,

Error response from daemon: Ports are not available: exposing port TCP 0.0.0.0:8888 -> 0.0.0.0:0: listen tcp4 0.0.0.0:8888: bind: address already in use

This command had worked as expected immediately before updating Docker Desktop. I tried completely killing docker and all associated processes, rebooting and rerunning the command but this error message always came up.

Share your logs (at least 10 lines)

There are no logs because gluetun won't start.

Share your configuration

gluetun:
  container_name: gluetun
  image: qmcgaw/gluetun:latest
  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-mapped from a:
    - 5055:5055
    ## Port-mapped from b:
    - 7878:7878
    ## Port-mapped from c:
    - 8989:8989
    ## Port-mapped from d:
    - 8787:8787
    ## Port-mapped from e
    - 6767:6767
    ## Port-mapped from f
    - 8080:8080
    - 9090:9090
  volumes:
    - ~/gluetun_docker:/gluetun
  environment: # See https://github.com/qdm12/gluetun/wiki
    # ProtonVPN
    - VPN_SERVICE_PROVIDER=protonvpn
    - VPN_TYPE=wireguard
    # 
    - VPN_ENDPOINT_IP=###########
    - VPN_ENDPOINT_PORT=#####
    - WIREGUARD_PUBLIC_KEY=#########################=
    - WIREGUARD_PRIVATE_KEY=#################################=
    - WIREGUARD_ADDRESSES=##########
    #
    - TZ=America/Chicago

[github-actions]

@qdm12 is more or less the only maintainer of this project and works on it in his free time.
Please:

• do not ask for updates, be patient
• 👍 the issue to show your support instead of commenting
  @qdm12 usually checks issues at least once a week, if this is a new urgent bug,
  revert to an older tagged container image

[atticusmatticus]

rolling back to docker desktop v4.34.3 fixes the issue temporarily.

[deboy69]

Same issue on ubuntu not sure if its gluetun related or docker

3rd reboot seemed to fix. Hmmm

[qdm12]

You have something else (old container, another container or a docker daemon bug) listening on port tcp 8888, that's a docker configuration issue and nothing to do with gluetun. Note you can change that port to another port in your ports: section for example 5678:8888/tcp

[github-actions]

Closed issues are NOT monitored, so commenting here is likely to be not seen.
If you think this is still unresolved and have more information to bring, please create another issue.

This is an automated comment setup because @qdm12 is the sole maintainer of this project
which became too popular to monitor issues closed.