Extension Manager Requires Docker

[Ryonez]

So I'm someone else having the above error.

The current compose file:

version: '2.4'
services:
  alteria-rem:
    container_name: alteria-rem
    network_mode: host
    group_add:
      - ${DOCKER_GID}
    environment:
        - TZ=Pacific/Auckland
    volumes:
        - /var/run/docker.sock:/var/run/docker.sock
        - '/mnt/user/appdata/alteria-rem/:/home/node/.rem/:rw'
    image: 'theappgineer/roon-extension-manager:v1.x-standalone'

The gui is set to the correct value, and I've confirmed that by going into the container and looking in the file location as well. Portainer is on this system, and can successfully connect and control docker, it is how I manage docker on this system.

[JanKoudijs]

A few remarks:

• Is the DOCKER_GID variable defined somewhere? You can also replace it with the group number, see Wiki how to get it
• You might have to change the container_name to roon-extension-manager, some functionality expects the container named that way

[Ryonez]

Okay, went through things and have some things that may help others, and some suggestions as well.

First thing I learned is /var/run/docker.sock (if fact any docker socket) can only be connected to once. This means if you're using Portainer to control it's host, it's fairly likely you are already using the default socket. There are options to run docker with other sockets, as documented here: Daemon socket option

Second is you're right, even once that's sorted I had issues due to the docker name not being what the container expected. This is the first time I've come across a container that require a specific name.

I'd recommend adding information on both of these to the install information, as it'd help a lot who have little to no experience with docker sockets, and those who've never come across containers that need set names.

As this has been figured out issue wise, I'll close it. Thank you for the help.