Is it possible to use tsbridge with non-bridge networks?

[auspex]

I have two remaining containers (out of about 30, so Go TSBridge!) I can't get to work with tsbridge.

One is network_mode: host (one of these days, I'll get it off there, but it'll just end up like the second one!), the other uses a macvlan network.

I suspect that there's nothing I can currently do to make tsbridge work with either of them, but just want to confirm that.

These are the two containers:

  atlas:
    container_name: atlas
    cap_add:
    - NET_RAW
    - NET_ADMIN
    volumes:
    - /var/run/docker.sock:/var/run/docker.sock
    image: keinstien/atlas:latest
    labels:
      tsbridge.enabled: true
      tsbridge.service.name: atlas
      tsbridge.service.port: 8888
      tsbridge.service.tls_mode: off
    network_mode: host
  homeassistant:
    container_name: homeassistant
    image: ghcr.io/home-assistant/home-assistant:stable
    volumes:
      - /srv/config/homeassistant:/config
      - /etc/localtime:/etc/localtime:ro
      - /run/dbus:/run/dbus:ro
    ports: 
      - 2869:2869/tcp
      - 1900:1900/udp
      - 5001:5001/tcp
      - 8123:8123
    cap_add: 
      - NET_ADMIN
      - NET_BIND_SERVICE
      - SYS_ADMIN
    networks:
      proxy:
      vlan:
    labels:
      - tsbridge.service.name=homeassistant
      - tsbridge.service.port=8123
      - tsbridge.service.tls_mode=off

The first has actually registered a 'machine' in tailscale, so maybe there's hope (though i'm not able to access it, except directly through the docker IP), the second doesn't even register with tailscale.

[jtdowney]

If the tsbridge container can reach the service container over the network, then I would expect there is a way to make it work. As for why the second one didn't register, it looks like it is missing tsbridge.enabled=true in the labels.

[auspex]

Lol! I have another stack where tsbridge.enabled is in a common yaml extension file...

I was sure there would be something stupid like that...

[auspex]

Yes, homeassistant now works.