Run OVOS-docker with bridge network

[simonh1005]

Hi OVOS community,
I am currently trying to get started with OVOS running in docker and therefore reading through the docs. I can see that the docker-compose files proposed there are all using the network mode host. As I try to prevent using host networks with docker, I would be interested if there is a way to run the container in the docker network. In best case, without even exposing the ports of the messagebus to the host. I tried to do this, but it seems that the other containers will not find the messagebus in this case:

voice - ovos_bus_client.client.client:on_error:114 - WARNING - Connection Refused. Is Messagebus Service running?

I assume that by default the docker containers are searching the messagebus on 127.0.0.1:8181. Is there any setting that allows me to change this and specify :8181 as URL for the messagebus on the other containers?

Here is my ansible playbook that I am currently using to set up the containers for reference. Interesting bit is where I use ovos_network as local docker bridge network:

- name: Create OVOS edge docker-network
  tags: install,ovos
  docker_network:
    name: ovos_network
...
- name: Ensure ovos_messagebus container is running
  tags: install,update,start,ovos
  docker_container:
    name: ovos_messagebus
    image: "smartgic/ovos-messagebus:latest"
    networks:
      - name: ovos_network
    volumes:
      - "{{ conf_dir }}/:/home/{{ app_user }}/.config/mycroft:ro"
      - "{{ base_dir }}/ovos/state:/home/{{ app_user }}/.local/state/mycroft"
      - "/tmp/mycroft:/tmp/mycroft"
    env:
      TZ: "{{ timezone | default('UTC') }}"
    labels:
      ovos.service: messagebus

- name: Ensure ovos_listener container is running
  tags: install,update,start,ovos
  docker_container:
    name: ovos_listener
    image: "smartgic/ovos-listener:latest"
    pull: "{{ update_docker_image | default(true) }}"
    restart_policy: unless-stopped
    networks:
      - name: ovos_network
    volumes:
      - "{{ conf_dir }}/:/home/{{ app_user }}/.config/mycroft:ro"
      - "{{ base_dir }}/ovos/records:/home/{{ app_user }}/.local/share/mycroft/listener"
      - "{{ base_dir }}/ovos/models:/home/{{ app_user }}/.local/share/precise-lite"
      - "{{ base_dir }}/ovos/vosk:/home/{{ app_user }}/.local/share/vosk"
      - "{{ base_dir }}/ovos/state:/home/{{ app_user }}/.local/state/mycroft"
      - "/tmp/mycroft:/tmp/mycroft"
    devices:
      - "/dev/snd"
    env:
      XDG_RUNTIME_DIR: "/run/user/{{ app_user_id.stdout }}"
      PULSE_SERVER: "unix:/run/user/{{ app_user_id.stdout }}/pulse/native"
      PULSE_COOKIE: "/home/{{ app_user }}/.config/pulse/cookie"
      TZ: "{{ timezone | default('UTC') }}"
    labels:
      ovos.service: listener

[JarbasAl]

You can set the host to point to your container https://github.com/OpenVoiceOS/ovos-config/blob/dev/ovos_config/mycroft.conf#L343

[simonh1005]

Thanks for this. I already tried it and it did not work. But if this is the correct setting, this is good to know and I will further investigate if the issue isn't somewhere else

[JarbasAl]

I know i set it up this way last year too, but didnt write any notes down unfortunately. I think i just had to share the OVOS network and set the container name in the mycroft.conf

the mycroft.conf needs to be mapped to every ovos container too

[simonh1005]

Just had time to look into this issue again and it indeed looks like the problem is not related to the docker networks. Instead, the messagebus is always binding to 127.0.0.1, no matter what I configure as "host" in mycroft.conf...
Will need to further investigate, why this is happening. I even tried with host "0.0.0.0", but it still binds to localhost only. Could there be some overwrites configured somehwere?

[simonh1005]

As the problem is not related to docker containers, I will close this thread and open a new one for the root problem.
@JarbasAl thank you for the help. Much appreciated

[simonh1005]

In case anyone else face similiar issues: In my case I assumed that the "messagebus" configures the messagebus, but indeed it is the "websocket" key as documented here.