On the compose plugin, line numbers don't match the lines of the YML.
That's why I say if I'm not mistaken, I'm not sure how to count lines, I started counting where the # ends
The error comes from 1 of the volumes which must be wrong
Well, I don't know what else to try. I had the OP delete the folder and recreate it, read the thread. Can you think of anything else to look at?
I'm on phone now.
I'll try to see it with better eyes latter and help the best I can, 😉
The only thing left to test is that the owner of the folder is appuser, but it shouldn't be necessary to do that.
The only thing left to test is that the owner of the folder is appuser, but it shouldn't be necessary to do that.
Or if the media is pointing to a specific place, 
Sorion , these are the points to check:
- The folder /SSD/appdata exists
- The folder /MEDIA/entertainment exists
- appuser has write permissions on both folders
- appuser has UID=1002 and GID=100
- Port 8888 is not busy in the system.
If you have doubts about checking any of the points, ask here.
If these points are checked and it still does not work, you have a sprite camped on the motherboard and its feet are on top of the CPU fan. Open the cover of the computer and get rid of the intruder.
Display MoreSorion , these are the points to check:
- The folder /SSD/appdata exists
- The folder /MEDIA/entertainment exists
- appuser has write permissions on both folders
- appuser has UID=1002 and GID=100
- Port 8888 is not busy in the system.
If you have doubts about checking any of the points, ask here.
If these points are checked and it still does not work, you have a sprite camped on the motherboard and its feet are on top of the CPU fan. Open the cover of the computer and get rid of the intruder.
Allright - I'm back.
I read all I missed so far and checked what I could nothing came up negativ so far.
Here is all the inputs back that should verify that even though I'm not sure about the permissions. I think it's okay?
$ cd /SSD
$ pwd
/SSD
$ cd /SSD/appdata
$ pwd
/SSD/appdata
$ cd /MEDIA/entertainment
$ pwd
/MEDIA/entertainment
$ ls -al /SSD/appdata
total 8
drwxrwsr-x 2 root users 4096 May 9 16:52 .
drwxr-xr-x 8 root root 4096 May 9 16:52 ..
$ ls -al /MEDIA/entertainment
total 0
drwxrwsr-x 1 sorion users 36 May 9 15:26 .
drwxrwsr-x 1 root users 26 May 9 15:27 ..
drwxrwsr-x 1 sorion users 11222 May 9 08:43 movies
drwxrwsr-x 1 sorion users 170888 May 6 12:27 music
drwxrwsr-x 1 sorion users 964 May 6 13:24 tvshows
$ id appuser
uid=1002(appuser) gid=100(users) groups=100(users),992(docker)sorion is just the user account for smb, but that shouldn't matter if I'm not stupid?
I have no idea how to check for port usage though.
Port forwarding is not used in my network as of now so for my understanding it must be in use by the server itself. I wouldn't know of anything but don't know how to verify that.
The only thing is that I had a portainer installation active when all this started which had a functioning jellyfin container which used port 8888 - but as of now to my knowledge everything in regards to that has been removed from the server.
I assume you're making a joke in regards to the cpu fan? If not I'm not following.
Unrelated to what you suggested I did also try to redo the syslinks and leave them out, as in use the mounting paths in the compose - didn't work either.
Edit:
Since that too was mentioned, I did check for timezone too:
$ timedatectl
Local time: Tue 2023-05-09 21:31:34 CEST
Universal time: Tue 2023-05-09 19:31:34 UTC
RTC time: Tue 2023-05-09 19:31:34
Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
NTP service: active
RTC in local TZ: noEven though it wouldn't make sense since the symlink is working I went and reconfirmed that both directorys are reachable under the non shorted link that I took from the symlink GUI page
$ cd /srv/dev-disk-by-uuid-4692ac63-fd6e-4884-b875-118de220d9a8/media/entertainment
$ pwd
/srv/dev-disk-by-uuid-4692ac63-fd6e-4884-b875-118de220d9a8/media/entertainment
$ cd /srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64bec
$ pwd
/srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64bec
$ ls
appdata aquota.group aquota.user backup backup_os compose docker lost+foundI assume you're making a joke in regards to the cpu fan? If not I'm not following.
It is a joke,
As for the rest, you are using the openmedia-compose plugin, correct?
You have already set a shared folder to work with the plugin?
My example:
That folder was created as a Shared-Folder since it's required by the Plugin (you can name it what you want)
Now, edit the YML like this:
---
version: "2.1"
services:
jellyfin:
image: lscr.io/linuxserver/jellyfin:latest
container_name: jellyfin
environment:
- PUID=1002
- PGID=100
- TZ=Europe/Berlin
- JELLYFIN_PublishedServerUrl=192.168.1.130 #Edit the LAN-IP with your own
volumes:
- /SSD/appdata/jellyfin/config:/config
- /MEDIA/entertainment/tvshows:/media/tvshows:ro
- /MEDIA/entertainment/movies:/media/movies:ro
- /MEDIA/entertainment/music:/media/music:ro
ports:
- 8096:8096
restart: unless-stoppedSave, accept the changes and click the check icon
If any error comes out, click on the bell on the TOP-RIGHT and paste the error.
If no error comes, access the GUI of jellyfin on a different PC with http://192.168.1.130:8096 (edit the LAN-IP to your's)
I assumed you had forgotten to ask for also "up"ing the file since without I couldn't possibly connect
Correct, I forgot to post that, 
But if you don't mind going into detail, would you mind explaining why this worked now?
This made the sprite take the feet of the CPU fan, 
(joking)
The container config folder was created, at deploy time, with a new folder that now, belongs to the proper ID that you wanted. This makes the container with the proper permissions, and cleans any error. It could be possible to move and assign the same permissions on the old folder but the trouble and time is just not worth it.
What is the ":ro" ending doing?
This is just a habit I have to only pass media folder with Read-Only attributes on these type of containers (Jellyfin, Emby, Plex, etc)
This is just to prevent that anyone, can be able to delete files from it. This flag is only INSIDE the container, NOT on the HOST.
Why did we have to add the published server ip when that apparently isn't usually necessary?
Although it says optional, I only managed to find the server on the LAN, if I have that environment setted. Makes it more visible on the LAN since it advertises to it:
Why the split into all 3 categorys instead of just refering to parent folder?
Again, this is my personal preference. This way, on the jellyfin GUI, I set each Library pointing to each of those folders individually.
But you can always edit the YML to use only the parent one. Up to you.
I assume I should going forwards setup all docker containers with compose - if I see a use in adding portainer for a GUI to the mix in the future, would you advice me to not do that for compability or security(?) concerns or should that be of no relevance?
I don't use Portainer for a long time. Always launched YMLs via command-line with docker-compose.
Since the Plugin simplifies it even more, I only use now, the plugin.
No point in having Portainer in use.
But this is just a choice. I see lot's of users only using Portainer, or Yacht or both.
This is just a way of running containers.
You should use what you like more or feel better using.
Thanks Soma . This thread was starting to make me lose sleep LOL
I assume you're making a joke in regards to the cpu fan? If not I'm not following.
Sure enough, this was just a joke. Possibly the culprit is my Mediterranean personality, I can't help it
- JELLYFIN_PublishedServerUrl=192.168.1.130 #Edit the LAN-IP with your own
I have never seen the need to use this setup. I take note, possibly I will add it to the guide.
It shouldn't make a difference to the container implementation anyway.
The only thing is that I had a portainer installation active when all this started which had a functioning jellyfin container which used port 8888 - but as of now to my knowledge everything in regards to that has been removed from the server.
I will change the theme of the port in the guide as well. I just changed it to illustrate that it's possible to do it, and how to do it. But seeing that this is not the first thread where he has created problems, it's not worth it.
The container config folder was created, at deploy time, with a new folder that now, belongs to the proper ID that you wanted. This makes the container with the proper permissions, and cleans any error. It could be possible to move and assign the same permissions on the old folder but the trouble and time is just not worth it.
What does this mean? The folder defined in the plugin is a standard OMV shared folder
owner: root
owner group: users
permissions: 775
And the subfolders and files within that folder are managed by the plugin with its own permissions.
Why would redoing that folder make a difference? I can't make sense of this.
- /MEDIA/entertainment/tvshows:/media/tvshows:ro
Separating or not separating the media folders is also not a reason for the container not to work. Nor the fact of configuring them as read-only. By the way, if you do that jellyfin won't be able to write to the movie folders the nfo files. If you don't use them everything will be fine.
____________________________________________________________________________
So I still don't understand where the goblin was. Can someone explain it to me as if I were a noob? Or maybe there really was a sprite?
As I reread this, a possible explanation comes to mind. It is possible that the old yaml file ended up badly formatted during the first edit. Copying and pasting this file again might have resolved it.
If no one contributes, I'll just keep this idea in my head.
As I reread this, a possible explanation comes to mind. It is possible that the old yaml file ended up badly formatted during the first edit. Copying and pasting this file again might have resolved it.
If no one contributes, I'll just keep this idea in my head.
unlikely. I did completely delete and remake the file a few times in between. After all I had to reinstall Docker which requires me to throw out compose too.
Pretty sure I copied my linked here one back but did also once go to the wiki and copy everything from there and reenter the inputs.
unlikely. I did completely delete and remake the file a few times in between. After all I had to reinstall Docker which requires me to throw out compose too.
Pretty sure I copied my linked here one back but did also once go to the wiki and copy everything from there and reenter the inputs.
So, if you are sure that this file was formatted correctly, I can't find a logical explanation for all this.
The folder defined in the plugin is a standard OMV shared folder
If you refer compose-plugin, that folder only holds the YML and ENV files created and nothing else.
As for the config folder of the container, I don't really have a proper answer as to why it works now.
When things aren't working proper, I rather have a fresh launch than chasing white-rabbits.
And since I saw that the symlink was pointing to the root of the drive, I felt it was better to start again.
IIRC, You say in your guide to make a SSD symlink to the root of a drive.
I think it's better to create a sub-folder on the drive first (eg. appdata) and then symlink to it, instead of the upper folder (the root of the drive).
When creating the config volumes, it will create the subfolders with the UID:GID mentioned on the YML.
I'm so use to this that I don't even think about other possible issues.
Same goes with the rest of the volumes.
Separating or not separating the media folders is also not a reason for the container not to work. Nor the fact of configuring them as read-only.
This was just a personal input. Doesn't mean it's mandatory,
Nor the fact of configuring them as read-only. By the way, if you do that jellyfin won't be able to write to the movie folders the nfo files.
Well, this is just me beeing paranoid in preventing someone to delete any of that MEDIA DATA (I mount it also RO on Nextcloud) in case of any hacking.
I rather have the DB and INFO on the appdata folder/drive (since it's a seperate SSD) and only reading from the MEDIA HDD than having CONTAINERS writing to that drive.
Nothing that can't be changed on (re)deployment of the container.
I can't give you better explanation than the above.
If you refer compose-plugin, that folder only holds the YML and ENV files created and nothing else.
I know. It is enough that they can be read.
As for the config folder of the container, I don't really have a proper answer as to why it works now.
Me neither
When things aren't working proper, I rather have a fresh launch than chasing white-rabbits.
I agree. Which is why I had the OP delete that folder and recreate it. It didn't work.
IIRC, You say in your guide to make a SSD symlink to the root of a drive.
I think it's better to create a sub-folder on the drive first (eg. appdata) and then symlink to it, instead of the upper folder (the root of the drive).
When creating the config volumes, it will create the subfolders with the UID:GID mentioned on the YML.
I'm so use to this that I don't even think about other possible issues.Same goes with the rest of the volumes.
You haven't read the guide You don't need it, it's normal that you haven't.
The procedure creates a symlink to the /SSD drive. Then create a shared folder, appdata. The container then creates the subfolder within appdata for each app.
It's the same thing you're saying. The only difference is where the symlink is referenced.
The same goes for user data. Creating symlinks to folders would complicate things.
The only reason to use symlinks in the procedure is to avoid the use of uuid's. Simplicity.
This was just a personal input. Doesn't mean it's mandatory,
I know. I was just looking for the goblin.
He who wants to deepen the use of docker can search in google.
Well, this is just me beeing paranoid in preventing someone to delete any of that MEDIA DATA (I mount it also RO on Nextcloud) in case of any hacking.
I rather have the DB and INFO on the appdata folder/drive (since it's a seperate SSD) and only reading from the MEDIA HDD than having CONTAINERS writing to that drive.
Same thing here, just looking for the goblin.
I can't give you better explanation than the above.
Then we only have the explanation of the goblin.
Then we only have the explanation of the goblin.
Those damn sprites are everywhere,
I will change the theme of the port in the guide as well. I just changed it to illustrate that it's possible to do it, and how to do it. But seeing that this is not the first thread where he has created problems, it's not worth it.
Modified in the guide, this will no longer cause problems.
- JELLYFIN_PublishedServerUrl=192.168.1.130 #Edit the LAN-IP with your own
I have never seen the need to use this setup. I take note, possibly I will add it to the guide.
Added this too. Thanks.
Modified in the guide, this will no longer cause problems.
Only saw the "new version" of it.
Nicely done,
ryecoaaron Maybe you should take a look at this.
Trying to reproduce the error in this thread I have done the following:
- new vm
- omv-extras installed
- openmediavault-compose installed
- openmediavault-symlink installed
- jellyfin container created in the GUI
Pressing the up button throws this error.
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-ddcb2839-7b76-4679-bba1-b975670cda31/compose//jellyfin/jellyfin.yml' --env-file '/srv/dev-disk-by-uuid-ddcb2839-7b76-4679-bba1-b975670cda31/compose//jellyfin/jellyfin.env' up -d 2>&1': sh: 1: docker-compose: not found
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-ddcb2839-7b76-4679-bba1-b975670cda31/compose//jellyfin/jellyfin.yml' --env-file '/srv/dev-disk-by-uuid-ddcb2839-7b76-4679-bba1-b975670cda31/compose//jellyfin/jellyfin.env' up -d 2>&1': sh: 1: docker-compose: not found in /usr/share/openmediavault/engined/rpc/compose.inc:330
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMVRpcServiceCompose->{closure}('/tmp/bgstatushL...', '/tmp/bgoutputjA...')
#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}check button
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-ddcb2839-7b76-4679-bba1-b975670cda31/compose//jellyfin/jellyfin.yml' --env-file '/srv/dev-disk-by-uuid-ddcb2839-7b76-4679-bba1-b975670cda31/compose//jellyfin/jellyfin.env' config 2>&1': sh: 1: docker-compose: not found
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-ddcb2839-7b76-4679-bba1-b975670cda31/compose//jellyfin/jellyfin.yml' --env-file '/srv/dev-disk-by-uuid-ddcb2839-7b76-4679-bba1-b975670cda31/compose//jellyfin/jellyfin.env' config 2>&1': sh: 1: docker-compose: not found in /usr/share/openmediavault/engined/rpc/compose.inc:330
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMVRpcServiceCompose->{closure}('/tmp/bgstatusBF...', '/tmp/bgoutputFt...')
#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}correct yaml file
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
# jellyfin
# media server
---
version: "2.1"
services:
jellyfin:
image: lscr.io/linuxserver/jellyfin:latest
container_name: jellyfin
environment:
- PUID=1002
- PGID=100
- TZ=Europe/Madrid
volumes:
- /SSD/appdata/jellyfin:/config
- /DATA/media:/media
ports:
- 8096:8096
restart: unless-stoppeddocker working
root@omv6-nas:~# systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-05-12 18:55:50 CEST; 1h 21min ago
TriggeredBy: ● docker.socket
Docs: https://docs.docker.com
Main PID: 1572 (dockerd)
Tasks: 8
Memory: 39.2M
CPU: 480ms
CGroup: /system.slice/docker.service
└─1572 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
may 12 18:55:49 omv6-nas systemd[1]: Starting Docker Application Container Engine...
may 12 18:55:49 omv6-nas dockerd[1572]: time="2023-05-12T18:55:49.663699234+02:00" level=info msg="Starting up"
may 12 18:55:49 omv6-nas dockerd[1572]: time="2023-05-12T18:55:49.758420141+02:00" level=info msg="Loading containers: start."
may 12 18:55:49 omv6-nas dockerd[1572]: time="2023-05-12T18:55:49.982562429+02:00" level=info msg="Loading containers: done."
may 12 18:55:50 omv6-nas dockerd[1572]: time="2023-05-12T18:55:50.015683047+02:00" level=info msg="Docker daemon" commit=9dbdbd4 graphdriver=overlay2 version=23.0.6
may 12 18:55:50 omv6-nas dockerd[1572]: time="2023-05-12T18:55:50.015785101+02:00" level=info msg="Daemon has completed initialization"
may 12 18:55:50 omv6-nas systemd[1]: Started Docker Application Container Engine.
may 12 18:55:50 omv6-nas dockerd[1572]: time="2023-05-12T18:55:50.044287900+02:00" level=info msg="API listen on /run/docker.sock"Reboot did nothing
What else can i watch?
docker-compose: not found
If I'm not mistaken, docker-compose command lost the -
It's now docker compose
Can check this better tomorrow
[EDIT]
Can you try this on CLI:
pi@panela:~ $ which docker-compose
/usr/local/bin/docker-compose
pi@panela:~ $ which docker compose
/usr/bin/docker
/usr/bin/compose
pi@panela:~ $ docker compose version
Docker Compose version v2.17.3
pi@panela:~ $ docker-compose version
Docker Compose version v2.17.3I recall seeing something refering the change on the command on one of the last updates of docker-cli but can't seem to find it.
I've been updating so it's shows both commands the same.
Since you made a fresh install, maybe the "new command" is different.
Don’t have an account yet? Register yourself now and be a part of our community!
