NetBrain Zwift Docker compability

[eskimos20]

Hi!

I have an Idea and I dont know if it is possible but with Kim Eiks docker image it is possible to Zwift on Linux with Docker.

But it is not using Bluetooth. Its using Zwift Companion app to connect your trainer, heart monitor and then use companion to talk to Zwift via Wifi.

Is it possible to use QZ app to connect to trainer, heart monitor, zwift click or zwift controllers and then use same interface that companion app uses to talk to zwift.

Would be great to use qz app on Linux and then run Zwift in Docker.

I can be a tester for this functionallity if you would like that.

/Eskimos

[cagnulein]

it's what qz is already doing. it's streaming via wifi using the wahoo virtual dircon interface

[eskimos20]

Yes, but itś somehow not working and Zwift/Docker is not seeing any interface. But If I connect my trainer to companion and in Zwift/Docker select, pair through phone that works as it should. But not in anyway qith QZ.

But It would be great if it would :)

[cagnulein]

@nix155 i guess it's because it's not open on the docker? are you forwarding all the tcp/udp port from the qz docker?
@eskimos20 if you run qz outside qz for sure it works

[eskimos20]

I will try that and get back to you. There are some docker options when building the image to use other network options. I will try :)

[nix155]

@eskimos20

Can you provide a link to the Zwift Docker image and the parameters for running the container?

As I understand it, the workflow is as follows:
It doesn't matter where you run QZ—it connects to the trainer via Bluetooth and transmits data to Zwift using the same Bluetooth connection.

According to this workflow, if Zwift uses Bluetooth to connect to QZ, you need to ensure that Zwift has access to the host's Bluetooth from within the container.

[cagnulein]

yes but we need also tcp and udp forwarding for dircon protocol

[eskimos20]

https://github.com/netbrain/zwift

Zwift does not use Bluetooth at all for this setup.

/Eskimos

[nix155]

In this case, to avoid port forwarding, the simplest option is to run the container in host mode:

• For Docker Compose, use:

  network_mode: host

• For docker run, use:

  docker run --network host ...

[eskimos20]

Yes I did that and it WORKED!! :)

Zwift Click did not work when I used the Get Gears option.. will try some other way though! :)

[cagnulein]

get gears requires both bluetooth and dircon as in my video. otherwise you have to pair it with qz directly.
i'm working on this in the #2961

[nix155]

Essentially, a container is the host's kernel combined with the libraries and hardware we’ve included in it. 🙂

[nix155]

Just in case—if you need to use the regular mode after all, check the ports used by QZ in host mode with:

ps -aux | grep 'qdom'

Then, forward these ports from the container using the appropriate -p option in docker run or the ports section in docker-compose.yml.

[eskimos20]

I got it all working in linux with netbrain/zwift in docker and qz app with gui. I could connect trainer, heart monitor and zwift click to the qz app via gui.

But earlier I used this for no gui version: ["qdomyos-zwift", "-no-gui", "-zwift_play_emulator", "-no-log"]

But i am not sure zwift_play_emulator will work now since no bluetooth is involved..is there an option for Zwift Click via command line?

And how do I connect my heart monitor without the gui selection?

/Eskimos

[cagnulein]

But i am not sure zwift_play_emulator will work now since no bluetooth is involved..is there an option for Zwift Click via command line?

it can't work for now.

And how do I connect my heart monitor without the gui selection?

you can set your HR to the settings file manually

[nix155]

If you're running applications on a laptop or a home computer with a monitor, you can run multiple GUI applications in Docker on Linux using X11 or Wayland by forwarding the X11 socket into those containers. I'll provide an example configuration a bit later.

[nix155]

We can run GUI applications inside a container and forward their GUI to the host. Before doing so, you need to grant access to the X11 socket:

xhost +local:docker

Here's an example docker-compose.yml configuration for running qdomyos-zwift with X11:

services:
  qdomyos-zwift-x11:
    image: ghcr.io/nix155/qdomyos-zwift-webgl
    container_name: qdomyos-zwift-x11
    privileged: true
    network_mode: "host"
    environment:
      - DISPLAY=${DISPLAY}
      - QT_SCALE_FACTOR=1.5       # Scale factor for the interface
      - QT_FONT_DPI=120           # DPI for fonts
      - QT_AUTO_SCREEN_SCALE_FACTOR=1
    volumes:
      - /dev:/dev
      - /run/dbus:/run/dbus
      - ./.config:/root/.config
      - /tmp/.X11-unix:/tmp/.X11-unix
    stdin_open: true
    tty: true
    restart: "no"
    command: ["qdomyos-zwift"]

Key Points:

1. Environment Variable for Display:

   environment:
     - DISPLAY=${DISPLAY}

   This forwards the X server's display environment variable to the container.

2. Volume for X11 Socket:

   volumes:
     - /tmp/.X11-unix:/tmp/.X11-unix

   This mounts the X11 socket directory so the container can communicate with the host's X server.

3. Host Network Mode:

   network_mode: "host"

   This ensures that the container uses the host's network stack, which is particularly useful for GUI applications.

With this setup, the GUI of qdomyos-zwift will be displayed on the host system.