[mpd] does not work

[LennyLip]

trying to start image without port and values mapping in portainer - got (bridge network):

exception: bind to '0.0.0.0:6600' failed (continuing anyway, because binding to '[::]:6600' succeeded): Failed to bind socket: Address in use
exception: Failed to open '/var/lib/mpd/database': No such file or directory
exception: Failed to configure output in line 23
exception: nested: No such audio output plugin: pulse

[DarkAxi0m]

Also got this, looking else where

[marcovitali]

trying to start image without port and values mapping in portainer - got (bridge network):

exception: bind to '0.0.0.0:6600' failed (continuing anyway, because binding to '[::]:6600' succeeded): Failed to bind socket: Address in use
exception: Failed to open '/var/lib/mpd/database': No such file or directory
exception: Failed to configure output in line 23
exception: nested: No such audio output plugin: pulse

You can solve the exception: bind to '0.0.0.0:6600' failed (continuing anyway, because binding to '[::]:6600' succeeded): Failed to bind socket: Address in use adding bind_to_address "0.0.0.0" in mpd.conf.

Relating to exception: Failed to open '/var/lib/mpd/database': No such file or directory I solved mounting /var/lib/mpd.

You have to check your audio_outputs in mpd.conf to solve the exception: nested: No such audio output plugin: pulse.

HOWEVER, the only way I'm able to start this container is using privileged: true, otherwise I have standard_init_linux.go:211: exec user process caused "operation not permitted". Does anyone know why? @vimagick could you help on this? Thank you.

[LJ-Software]

@marcovitali after messing with individual capability flags on the docker container I have found that the needed option to be used to avoid the standard_init_linux.go:211: exec user process caused "operation not permitted" is SYS_NICE.

I do not recommend running the container with privileged: true as this is a security concern.

[marcovitali]

@marcovitali after messing with individual capability flags on the docker container I have found that the needed option to be used to avoid the standard_init_linux.go:211: exec user process caused "operation not permitted" is SYS_NICE.

I do not recommend running the container with privileged: true as this is a security concern.

@LJ-Software Thank you for the suggestion. I agree with you, but privileged=true was the only way. Now I have removed it. I had not tried with capabilities.

Now I have only the error avahi: Failed to create client: Daemon not running on container startup, but all works correctly.

[radusuciu]

+1

Seems like this error persists to this day..

[JCapriotti]

FWIW, it seems like the location for the mpd.conf file changed.

The "config" volume specified in the example docker-compose.yml needs to change from:

./data/config:/root/.config

to:

./data/config:/root/.mpd

Once I made that change everything worked.