Ah cool, the docs made it sound like container: uses the container ID hash instead of the name so I wasn’t sure how that works. I just put stuff like this in the same compose file since they’re all closely related.
Comment on Torrenting behind gluetun on zimaos?
theorychapter@sh.itjust.works 3 days agoIdk how zimaos works, but the way to attach containers like this is with
network_mode: “service:othercontainer”which might need them to be in the same compose file (the docs aren’t clear).
network_mode: “container:gluetun”
Is how you can do it with separate compose files. And yes you’d need to map the ports in the gluetun compose file for any container you route through gluetun.
BakedCatboy@lemmy.ml 3 days ago
ayyo@sh.itjust.works 3 days ago
Ohhh this might be my issue. I’ll have to try it tonight