Auto Update Error Question

[brikim]

@kmendell I didn't want to write a bug just wanted to ask first.

I have a VPN project that contains a few containers. Gluetun (VPN) and a few containers that use the VPN network. One of the other containers in this project had an image update and was set to auto-update but there was an error. The containers failed to start with the below message. I can restart the other_container on the Containers page by doing a Down then Up and it restarts ok.

Not sure if this is from docker itself or an arcane message.

{
  "container": "prowlarr",
  "containerId": "bbfd779fa28e6b9d8b57fe7aeb1728c06b33ef0c5ebf08f9e15d1580c2b39389",
  "error": "create: Error response from daemon: conflicting options: hostname and the network mode",
  "newImageMain": "lscr.io/linuxserver/prowlarr:latest",
  "oldImageMain": "sha256:4637dd36c21c6649eb79d95da2a6ef50b206de8ba9cca5ca8c84f4cacdc055f5",
  "phase": "container",
  "status": "failed"
}

I took a snip of the compose file

---
services:
  gluetun:
    image: qmcgaw/gluetun:latest
    container_name: gluetun
    restart: unless-stopped
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun:/dev/net/tun
    ports:
      - xxx:xxx/tcp # port for prowlarr
    volumes:
      - xxxx
    networks:
      container-bridge:
        ipv4_address: xxx.xxx.xxx.xxx
    environment:
      - VPN_SERVICE_PROVIDER=xxx
      - VPN_TYPE=wireguard
      - WIREGUARD_PRIVATE_KEY="xxx"
      - WIREGUARD_ADDRESSES="xxx"
      - SERVER_HOSTNAMES="xxx"
      - TZ=xxx
      
  other_container:
    container_name: other_container
    image: lscr.io/linuxserver/other_container:latest
    network_mode: service:gluetun # run on the gluetun vpn network
    security_opt:
      - no-new-privileges:true
    environment:
      - PUID=xxx
      - PGID=xxx
      - TZ=xxx
    volumes:
      - ./other_container:/config
    depends_on:
      gluetun:
        condition: service_healthy

Thanks for any help

[kmendell]

It was a bug and its fixed here :) f267dce

[brikim]

@kmendell Thx so much!

[brikim]

@kmendell I updated to the latest and removed my tags when a container tried to update in my stack I got a different error.

{
"id": "c4b5861c-96c8-43cf-a4fe-60225ab8e4e4",
"type": "system.auto_update",
"severity": "error",
"title": "Auto-update: container speedtest-tracker-vpn",
"resourceType": "system",
"resourceName": "auto_updater",
"environmentId": "0",
"metadata": {
"container": "speedtest-tracker-vpn",
"containerId": "2f1d0d7b9922a93a62ca1a43ae7ddb9fb46162d80a4f110ac388cc70817a7f05",
"error": "create: Error response from daemon: conflicting options: port exposing and the container type network mode",
"newImageMain": "lscr.io/linuxserver/speedtest-tracker:latest",
"oldImageMain": "sha256:64ff08a2bba32772a13d1baa8995c993fb3d86401db2562ca0b3f98cb89dd250",
"phase": "container",
"status": "failed"
},
"timestamp": "2025-11-30T09:57:46.384507752-06:00",
"createdAt": "2025-11-30T09:57:46.384507875-06:00",
"updatedAt": "2025-11-30T15:57:46.384594102Z"
}

[brikim]

I have a port exposed for gluetun but not for the prowlarr container within the same project