Docker error on creating container - path with "//"

Hello,

as i am installing OMV on a new computer, I followed the Docker guide thoroughly (this one [How to] Docker in OMV )

But i am facing a very strange issue when trying to "up" the container, i get an "error 500 . Internal server Error", with details attached further :

where i can’t help but notice this path, multiple times :

/srv/dev-disk-by-uuid-0a720522-1763-41fb-bd41-54b07938dd5a/dockcmp//jellyfin/jellyfin.yml'

i tried recreating the folder dockcmp with an other name : same issue

i tried with qbittorrent docker image : same double-slash issue

am i following a wrong trail?

Thanks a lot for your time

Zitat

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker-compose --file '/srv/dev-disk-by-uuid-0a720522-1763-41fb-bd41-54b07938dd5a/dockcmp//jellyfin/jellyfin.yml' --env-file '/srv/dev-disk-by-uuid-0a720522-1763-41fb-bd41-54b07938dd5a/dockcmp//jellyfin/jellyfin.env' up -d 2>&1': Network jellyfin_default Creating

Network jellyfin_default Created

Container jellyfin Creating

Container jellyfin Created

Container jellyfin Starting

Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: unable to apply apparmor profile: apparmor failed to apply profile: write /proc/self/attr/apparmor/exec: no such file or directory: unknown

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker-compose --file '/srv/dev-disk-by-uuid-0a720522-1763-41fb-bd41-54b07938dd5a/dockcmp//jellyfin/jellyfin.yml' --env-file '/srv/dev-disk-by-uuid-0a720522-1763-41fb-bd41-54b07938dd5a/dockcmp//jellyfin/jellyfin.env' up -d 2>&1': Network jellyfin_default Creating

Network jellyfin_default Created

Container jellyfin Creating

Container jellyfin Created

Container jellyfin Starting

Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: unable to apply apparmor profile: apparmor failed to apply profile: write /proc/self/attr/apparmor/exec: no such file or directory: unknown in /usr/share/openmediavault/engined/rpc/compose.inc:330

Stack trace:

#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMVRpcServiceCompose->{closure}('/tmp/bgstatusAL...', '/tmp/bgoutput14...')

#1 /usr/share/openmediavault/engined/rpc/compose.inc(333): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))

#2 [internal function]: OMVRpcServiceCompose->doCommand(Array, Array)

#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)

#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('doCommand', Array, Array)

#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Compose', 'doCommand', Array, Array, 1)

#6 {main}

Alles anzeigen

Hello,

thanks everyone for the help

Wolf2000 Yes, that’s what i meant, but i don’t understand why the system would use "//" and where to change it?

chente as advised I disabled apparmor, i am now able to create and up the container for qbittorrent. but still getting the same error for jellyfin, i also tried plex, but same "error 500 internal server error" ...

BernH  Soma

i am using the compose and symlink plugins, exactly as advised in "how-to-docker-in-omv".

here are the compose file for qbittorrent (working) and jellyfin (not working) :

---
version: "2.1"
services:
  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrent
    environment:
      - PUID=1000
      - PGID=100
      - TZ=Europe/Paris
      - WEBUI_PORT=8080
    volumes:
      - /disknvme/config/qbittorrent:/config
      - /dl:/downloads
    ports:
      - 8080:8080
      - 6881:6881
      - 6881:6881/udp
    restart: unless-stopped

---
version: "2.1"
services:
  jellyfin:
    image: lscr.io/linuxserver/jellyfin:latest
    container_name: jellyfin
    environment:
      - PUID=1000
      - PGID=100
      - TZ=Europe/Paris
    volumes:
      - /disknvme/config/Jellyfin:/config
      - /medias:/medias
    ports:
      - 8888:8096
    restart: unless-stopped

Zitat von chente

How do you know it doesn't work? What is wrong?

Maybe you just can't find a way to access it. Have you checked in Portainer if the container is working? Are you using the correct port in your browser? You established 8888 in your stack.

^Hello,

^{yes i tried in my browser, (also after putting the port back to 8096)}

^{the container isn’t even present in the compose containers :}

Zitat von Soma

I know you're using the compose plugin, the error comes from the OMV Gui (from the apply settings).

The reason I wanted to see the YML is due to the plugin beeing a bit picky with the idents, although the error doesn't mean come from that.

As for the double slashes // on errors from the plugin, it's normal, there's nothing to be changed.

Now for the real error, as chente already mentioned on #4, your system need the docker fix applied.

If qbit is functioning, restart the PC and see if it runs normal.

Then, try to launch jellyfin but use the normal port 8096.

For ref, here's the YML I use:

Code

---
version: "2.1"
services:
  jellyfin:
    image: lscr.io/linuxserver/jellyfin:latest
    container_name: jellyfin
    environment:
      - PUID=1000
      - PGID=100
      - TZ=Europe/Lisbon
      - JELLYFIN_PublishedServerUrl=192.168.1.130 #optional
    volumes:
      - /appdata/jellyfin/config:/config
      - /pote-media/TVshows:/data/tvshows:ro
      - /pote-media/Movies:/data/movies:ro
      - /pote-media/Anime:/data/anime:ro
      - /pote-media/Documentaries:/data/documentaries:ro
      - /pote-media/Music:/data/music:ro
    ports:
      - 8096:8096
    restart: unless-stopped

Alles anzeigen

chente

With the compose plugin, there's no need to have Portainer installed.

Just check the status of the containers on the OMV Gui:

Alles anzeigen

thank you for all the details, i already have rebooted a few times, changed port to 8096,

but still, container qbittorrent starts without any errors, but jellyfin doesn’t...

My install was absolutely new, so i decided to reinstall the whole system. and i still get the same error...

also I don’t know if it is related but i get this error on boot, i have to ctrl+d to force start :

also, if this might help, i am using a 2TB SSD, that i partitionned with 20GB for OMV system, and the rest for data.

but i don’t see how it would interact with docker

Sooooo....

First of all, thanks a lot for your help!

It took me almost all day, but it finally works!

Going back to the beginning, i narrowed down that my mounting problem came from the partition i did on the system disk. (no boot up error message when i removed it from filesystem in gui)

Most probably from the way i did it : install OMV via omv.iso, and then with a gparted live usb, reduced the partition.

So i installed OMV from scratch again, but using the debian minimal this time, making the partitions during installation "the right way". Then "upgrading" it to OMV.

did the workaround for apparmor

and jellyfin’s container went up on the first click

Trying to install OMV on this small optiplex computer, tryig to minimze the number of disks, definitely brought some pain!

(now begins the hard part, i was planning on trying to use SWAG, and maybe encrypted partition )

have a great evening!