Jump to content

Can't start emby-server in LXC container


Recommended Posts

ymyinfinity
Posted

Hello all,

I have a ubuntu 22.04 LTS container running on a proxmox installation.

I just installed emby via the .deb installer within the container, however I am unable to (re)start the emby-server, receiving the following error message:

...skipping...
x emby-server.service - Emby Server is a personal media server with apps on just about every device
     Loaded: loaded (/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Wed 2023-01-04 20:57:17 UTC; 2s ago
    Process: 3004 ExecStart=/opt/emby-server/bin/emby-server (code=exited, status=216/GROUP)
   Main PID: 3004 (code=exited, status=216/GROUP)
        CPU: 1ms

Jan 04 20:57:17 nas systemd[1]: Started Emby Server is a personal media server with apps on just about every device.
Jan 04 20:57:17 nas systemd[3004]: emby-server.service: Failed to determine supplementary groups: Invalid argument
Jan 04 20:57:17 nas systemd[3004]: emby-server.service: Failed at step GROUP spawning /opt/emby-server/bin/emby-server:>
Jan 04 20:57:17 nas systemd[1]: emby-server.service: Main process exited, code=exited, status=216/GROUP
Jan 04 20:57:17 nas systemd[1]: emby-server.service: Failed with result 'exit-code'.

I have looked at the emby-server file and confirmed it is owned by root:root, so I am unsure why it is not starting. I've noticed many users who are already discussing pass-through hardware acceleration, so I would be very grateful on how to get past this step!

It is an unprivileged container if that matters.

ymyinfinity
Posted

I found official guidance for another service (cPanel in a container) that they strongly recommend using privileged containers to avoid issues with services. 

As such I created a privileged ubuntu container and installed emby using the same steps and was up and running within 30 seconds.

 

Though proxmox recommends using unprivileged containers with U/GID mappings for security, it seems giving emby a privileged container to work in is the smoothest way forward.

  • Thanks 1
Posted

Thanks for following up !

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...