Unheathy container all of a sudden after months of no issues

[thenorman138]

I noticed this morning after a portainer reboot that my transmission instance wasn't working or being reached. I checked and the container is unhealthy with logs showing errors. My stack as is:

`---
version: "3.3"
services:
transmission-openvpn:
container_name: transmission-openvpn-syno
restart: always
cap_add:
- NET_ADMIN # This runs the container with raised privileges
devices:
- /dev/net/tun # This creates a tunnel for Transmission
volumes:
- /srv/27829c9c-dbc1-4408-a111-56dbcd8f0ec0/torrents/:/data # Change this to your Torrent path
environment:
- OPENVPN_PROVIDER=PIA
- OPENVPN_CONFIG=france
- OPENVPN_USERNAME=omitted
- OPENVPN_PASSWORD=omitted
- LOCAL_NETWORK=192.168.1.0/24
- OPENVPN_OPTS=--inactive 3600 --ping 10 --ping-exit 60 # Leave this as is
- PUID=998 #Change to your PUID
- PGID=100 #Change to your PGID

logging:
  driver: json-file
  options:
        max-size: 10m
ports:
  - '90:90'
image: haugene/transmission-openvpn
    
    `

Logs are:

Using OpenVPN provider: PIA Running with VPN_CONFIG_SOURCE auto No bundled config script found for PIA. Defaulting to external config Downloading configs from https://github.com/haugene/vpn-configs-contrib/archive/main.zip into /tmp/tmp.lwmUWYnAeC curl: (6) getaddrinfo() thread failed to start ./etc/openvpn/fetch-external-configs.sh: line 18: config_repo_temp_dir: unbound variable Starting container with revision: b33d0fe4c938259a0d4eb844e55468f387456121 WARNING: initial DNS resolution test failed Creating TUN device /dev/net/tun /etc/openvpn/start.sh: line 34: 10 Aborted (core dumped) nslookup ${HEALTH_CHECK_HOST:-"google.com"} > /dev/null 2>&1

Am I missing something from an update?

[thenorman138]

NVM, just saw the issue and added the security option to my stack and it works now

security_opt:

• seccomp:unconfined