Any way you can publish a container with just Windscribe that is meant to attach to other containers?

[connwork]

Main problem to solve here is that Windscribe hasn't yet implemented static port forwarding for WireGuard configs. I'm assuming your base Windscribe setup allows WireGuard connections, which would solve the issue. I just don't want to be tied to Deluge (Qbit seems better for overall management).

Other Windscribe dockers are under-maintained (ie, WiOrca's comment here). Your container seems very stable in comparison.

Would love something that could be implemented like (example with standalone windscribe image with a qbittorrent docker bound to it):

version: "3" services: windscribe: restart: unless-stopped image: kabe0/windscribe:latest volumes:

• /config:/config ports:
• 8989:8989 #Windscribe port
• 8090:8090 # Qbittorrent UI port
• 12345:12345 # Qbittorrent port
• 12345:12345/udp # Qbittorrent port cap_add:
• NET_ADMIN
• SYS_MODULE qbittorrent: image: lscr.io/linuxserver/qbittorrent:latest container_name: qbittorrent environment:
• PUID=1000
• PGID=1000
• TZ=1234
• WEBUI_PORT=8090 volumes:
• /config:/config
• /downloads:/downloads sysctls:
• net.ipv4.conf.all.src_valid_mark=1 restart: unless-stopped depends_on:
• windscribe network_mode: service:windscribe