Change PUID on container after the install - Permission issues?

Sorion · May 9th 2023

Do I have to create the jellyfin folder within appdata ahead of time? I assume not?

I did as you asked

1. removed the existing shared folder

2. removed the folder via rm -d /SSD/appdata from SSH account - that did require me to sudo it

3. confirmed folder is indeed gone

4. recreated folder via the GUI and shared folders

5. checked for:

Code

$ 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 ..

6. ran the container and got the same error

chente · May 9th 2023

Quote from Sorion

Do I have to create the jellyfin folder within appdata ahead of time? I assume not?

It is not necessary, docker creates up to one level of folders

Let's see if docker is working.

systemctl status docker.service

Sorion · May 9th 2023

Quote from chente

It is not necessary, docker creates up to one level of folders

Let's see if docker is working.
systemctl status docker.service

Well, that seems like something

Code

$ systemctl status docker.service
WARNING: terminal is not fully functional
-  (press RETURN)● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/docker.service.d
             └─waitAllMounts.conf
     Active: active (running) since Tue 2023-05-09 17:22:07 CEST; 4min 48s ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
   Main PID: 12678 (dockerd)
      Tasks: 13
     Memory: 39.4M
        CPU: 727ms
     CGroup: /system.slice/docker.service
             └─12678 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

Display More

Sorion · May 9th 2023

As mentioned beforehand I get an error everytime I install docker - I was not able to find it so I reproduced that error. The following is the the full copy of the console entry that goes by while installing, errors in the end.

I'm still in the process of finding the stuff in the syslogs.

Code

Docker storage :: /srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64bec/docker
Agent port:: 8000
Web port:: 9000
Yacht port:: 8001
ee:: 0
image:: portainer/portainer-ce
Enable TLS:: 0
arch   :: amd64
option :: docker
state  :: install
extras :: 6.1.1
DNS OK.
Create override directory ...
Create override file ...
mode of '/etc/systemd/system/docker.service.d/waitAllMounts.conf' changed from 0666 (rw-rw-rw-) to 0644 (rw-r--r--)
Reload systemd daemon ...
Get:1 file:/var/cache/openmediavault/archives  InRelease
Ign:1 file:/var/cache/openmediavault/archives  InRelease
Get:2 file:/var/cache/openmediavault/archives  Release
Ign:2 file:/var/cache/openmediavault/archives  Release
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Ign:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Get:3 file:/var/cache/openmediavault/archives  Packages
Get:4 file:/var/cache/openmediavault/archives  Translation-en
Ign:4 file:/var/cache/openmediavault/archives  Translation-en
Hit:5 http://deb.debian.org/debian bullseye InRelease
Get:6 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Hit:7 http://security.debian.org/debian-security bullseye-security InRelease
Hit:8 https://openmediavault-plugin-developers.github.io/packages/debian shaitan InRelease
Hit:9 https://packages.openmediavault.org/public shaitan InRelease
Get:10 https://deb.debian.org/debian bullseye-backports InRelease [49.0 kB]
Hit:11 https://download.docker.com/linux/debian bullseye InRelease
Fetched 93.0 kB in 2s (44.5 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  containerd.io docker-ce-cli
Suggested packages:
  aufs-tools cgroupfs-mount | cgroup-lite
Recommended packages:
  apparmor docker-ce-rootless-extras git libltdl7 pigz docker-buildx-plugin
The following NEW packages will be installed:
  containerd.io docker-ce docker-ce-cli docker-compose-plugin
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/74.4 MB of archives.
After this operation, 305 MB of additional disk space will be used.
Selecting previously unselected package containerd.io.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 41465 files and directories currently installed.)
Preparing to unpack .../containerd.io_1.6.21-1_amd64.deb ...
Unpacking containerd.io (1.6.21-1) ...
Selecting previously unselected package docker-ce-cli.
Preparing to unpack .../docker-ce-cli_5%3a23.0.6-1~debian.11~bullseye_amd64.deb ...
Unpacking docker-ce-cli (5:23.0.6-1~debian.11~bullseye) ...
Selecting previously unselected package docker-ce.
Preparing to unpack .../docker-ce_5%3a23.0.6-1~debian.11~bullseye_amd64.deb ...
Unpacking docker-ce (5:23.0.6-1~debian.11~bullseye) ...
Selecting previously unselected package docker-compose-plugin.
Preparing to unpack .../docker-compose-plugin_2.17.3-1~debian.11~bullseye_amd64.deb ...
Unpacking docker-compose-plugin (2.17.3-1~debian.11~bullseye) ...
Setting up containerd.io (1.6.21-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/containerd.service → /lib/systemd/system/containerd.service.
Setting up docker-compose-plugin (2.17.3-1~debian.11~bullseye) ...
Setting up docker-ce-cli (5:23.0.6-1~debian.11~bullseye) ...
Setting up docker-ce (5:23.0.6-1~debian.11~bullseye) ...
Created symlink /etc/systemd/system/multi-user.target.wants/docker.service → /lib/systemd/system/docker.service.
Created symlink /etc/systemd/system/sockets.target.wants/docker.socket → /lib/systemd/system/docker.socket.
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/docker.service.d
             └─waitAllMounts.conf
     Active: activating (auto-restart) (Result: exit-code) since Tue 2023-05-09 17:10:13 CEST; 6ms ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
    Process: 8577 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
   Main PID: 8577 (code=exited, status=1/FAILURE)
        CPU: 95ms
dpkg: error processing package docker-ce (--configure):
 installed docker-ce package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 docker-ce
Failed to install docker.
Try fixing install...
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up docker-ce (5:23.0.6-1~debian.11~bullseye) ...
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/docker.service.d
             └─waitAllMounts.conf
     Active: activating (auto-restart) (Result: exit-code) since Tue 2023-05-09 17:10:18 CEST; 9ms ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
    Process: 8690 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
   Main PID: 8690 (code=exited, status=1/FAILURE)
        CPU: 173ms
dpkg: error processing package docker-ce (--configure):
 installed docker-ce package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 docker-ce

** CONNECTION LOST **

Display More

chente · May 9th 2023

Quote from Sorion

Well, that seems like something

Is your server amd64? if so try this RE: docker not working since omv-upgrade

Sorion · May 9th 2023

Quote from chente

Is your server amd64? if so try this RE: docker not working since omv-upgrade

I am not entirely sure what you're asking for and that's a yes or not.

I have an Intel i7 4770K installed so if you're asking for amd architecture that should be a clear no though.

chente · May 9th 2023

Quote from Sorion

I have an Intel i7 4770K installed so if you're asking for amd architecture that should be a clear no though.

Intel i/7 is AMD64 architecture. AMD64 means 64bit.

You can apply post 9 of that thread.

Sorion · May 9th 2023

Quote from chente

Intel i/7 is AMD64 architecture. AMD64 means 64bit.
You can apply post 9 of that thread.

Okay. I kicked docker and compose off the system.

Applied the steps from the post and for the first time had no issue installing docker it would just run through without issue.

But, I still get the same issue.

Checking if docker runs properly as per your prompt from earlier still returns:

Code

$ systemctl status docker.service
WARNING: terminal is not fully functional
-  (press RETURN)● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/docker.service.d
             └─waitAllMounts.conf
     Active: active (running) since Tue 2023-05-09 17:59:23 CEST; 1min 14s ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
   Main PID: 2071 (dockerd)
      Tasks: 13
     Memory: 32.1M
        CPU: 752ms
     CGroup: /system.slice/docker.service
             └─2071 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

Display More

chente · May 9th 2023

Have you restarted the server?

Did you uninstall docker and reinstall it after reboot?

Sorion · May 9th 2023

Quote from chente

Have you restarted the server?
Did you uninstall docker and reinstall it after reboot?

I uninstalled compose then docker

then i executed all the commands which include a reboot at the end anyway.

I then reinstalled docker and then compose

chente · May 9th 2023

Run these two commands in succession and post the output.

systemctl status docker.service

journalctl -xe

Sorion · May 9th 2023

Quote from chente

Run these two commands in succession and post the output.

systemctl status docker.service
journalctl -xe

systemctl status docker.service:

Code

$ systemctl status docker.service
WARNING: terminal is not fully functional
-  (press RETURN)● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/docker.service.d
             └─waitAllMounts.conf
     Active: active (running) since Tue 2023-05-09 17:59:23 CEST; 11min ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
   Main PID: 2071 (dockerd)
      Tasks: 13
     Memory: 40.2M
        CPU: 898ms
     CGroup: /system.slice/docker.service
             └─2071 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
$

Display More

journalctl -xe:

Code

$ journalctl -xe
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal' can see all messages.
      Pass -q to turn off this notice.
WARNING: terminal is not fully functional
-  (press RETURN)May 09 15:18:26 dh-sv sshd[9441]: Disconnected from user dh_user 192.168.178.32 port 64243
May 09 15:18:57 dh-sv sudo[18090]:  dh_user : TTY=pts/0 ; PWD=/ ; USER=root ; COMMAND=/usr/bin/ls -al /SSD/docker
May 09 15:18:57 dh-sv sudo[18090]: pam_unix(sudo:session): session opened for user root(uid=0) by dh_user(uid=1001)
May 09 15:18:57 dh-sv sudo[18090]: pam_unix(sudo:session): session closed for user root
-- Boot 66f47bd054224d41a40302c3a7f4f743 --
May 09 16:37:25 dh-sv sudo[10571]:  dh_user : TTY=pts/0 ; PWD=/srv/dev-disk-by-uuid-4692ac63-fd6e-4884-b875-118de220d9a>
May 09 16:37:25 dh-sv sudo[10571]: pam_unix(sudo:session): session opened for user root(uid=0) by dh_user(uid=1001)
May 09 16:37:25 dh-sv sudo[10571]: pam_unix(sudo:session): session closed for user root
-- Boot 366dc1b8ebf84f4e882055140ba773e4 --
May 09 16:50:01 dh-sv sudo[3205]:  dh_user : TTY=pts/0 ; PWD=/srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64bec>
May 09 16:50:01 dh-sv sudo[3205]: pam_unix(sudo:session): session opened for user root(uid=0) by dh_user(uid=1001)
May 09 16:50:01 dh-sv sudo[3205]: pam_unix(sudo:session): session closed for user root
May 09 17:46:35 dh-sv sudo[16247]: pam_unix(sudo:auth): authentication failure; logname=dh_user uid=1001 euid=0 tty=/de>
May 09 17:46:44 dh-sv sudo[16247]:  dh_user : TTY=pts/0 ; PWD=/srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64be>
May 09 17:46:44 dh-sv sudo[16247]: pam_unix(sudo:session): session opened for user root(uid=0) by dh_user(uid=1001)
May 09 17:46:44 dh-sv sudo[16247]: pam_unix(sudo:session): session closed for user root
May 09 17:47:34 dh-sv sudo[16425]:  dh_user : TTY=pts/0 ; PWD=/srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64be>
May 09 17:47:34 dh-sv sudo[16425]: pam_unix(sudo:session): session opened for user root(uid=0) by dh_user(uid=1001)
May 09 17:47:34 dh-sv sudo[16425]: pam_unix(sudo:session): session closed for user root
May 09 17:48:03 dh-sv sudo[16464]:  dh_user : TTY=pts/0 ; PWD=/srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64be>
May 09 17:48:03 dh-sv sudo[16464]: pam_unix(sudo:session): session opened for user root(uid=0) by dh_user(uid=1001)
May 09 17:48:06 dh-sv sudo[16464]: pam_unix(sudo:session): session closed for user root
May 09 17:48:14 dh-sv sudo[17010]:  dh_user : TTY=pts/0 ; PWD=/srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64be>
May 09 17:48:14 dh-sv sudo[17010]: pam_unix(sudo:session): session opened for user root(uid=0) by dh_user(uid=1001)
May 09 17:48:14 dh-sv sudo[17010]: pam_unix(sudo:session): session closed for user root
-- Boot e8853a44f748448b9a055f6c5a29a028 --
May 09 17:51:04 dh-sv sudo[3035]:  dh_user : TTY=pts/0 ; PWD=/ ; USER=root ; COMMAND=/usr/bin/mkdir -p /etc/default/gru>
May 09 17:51:04 dh-sv sudo[3035]: pam_unix(sudo:session): session opened for user root(uid=0) by dh_user(uid=1001)
May 09 17:51:04 dh-sv sudo[3035]: pam_unix(sudo:session): session closed for user root
May 09 17:51:12 dh-sv sudo[3052]:  dh_user : TTY=pts/0 ; PWD=/ ; USER=root ; COMMAND=/usr/bin/tee /etc/default/grub.d/a>
May 09 17:51:12 dh-sv sudo[3052]: pam_unix(sudo:session): session opened for user root(uid=0) by dh_user(uid=1001)
May 09 17:51:12 dh-sv sudo[3052]: pam_unix(sudo:session): session closed for user root
May 09 17:51:18 dh-sv sudo[3063]:  dh_user : TTY=pts/0 ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/update-grub
May 09 17:51:18 dh-sv sudo[3063]: pam_unix(sudo:session): session opened for user root(uid=0) by dh_user(uid=1001)
May 09 17:51:20 dh-sv sudo[3063]: pam_unix(sudo:session): session closed for user root
May 09 17:51:26 dh-sv sudo[3603]:  dh_user : TTY=pts/0 ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/reboot
May 09 17:51:26 dh-sv sudo[3603]: pam_unix(sudo:session): session opened for user root(uid=0) by dh_user(uid=1001)
May 09 17:51:26 dh-sv sudo[3603]: pam_unix(sudo:session): session closed for user root
lines 37-74/74 (END)

Display More

Soma · May 9th 2023

Prepend sudo to the commands or run as root

chente · May 9th 2023

Quote from Sorion

lines 37-74/74 (END)

It is not complete, you have to press AvPag (this is Spanish, I don't know what that key is called in English) Page forward and page back.

Sorion · May 9th 2023

Quote from Soma

Prepend sudo to the commands or run as root

duh ... sorry - I'm an idiot apparently - not sure if I'm doing shit wrong but this prints out a looooooooooot of weird things:

sudo systemctl status docker.service:

Code

 docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset>
    Drop-In: /etc/systemd/system/docker.service.d
             └─waitAllMounts.conf
     Active: active (running) since Tue 2023-05-09 17:59:23 CEST; 21min ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
   Main PID: 2071 (dockerd)
      Tasks: 13
     Memory: 40.2M
        CPU: 1.048s
     CGroup: /system.slice/docker.service
             └─2071 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/cont>

May 09 17:59:22 dh-sv systemd[1]: Starting Docker Application Container Engine.>
May 09 17:59:22 dh-sv dockerd[2071]: time="2023-05-09T17:59:22.727058133+02:00">
May 09 17:59:22 dh-sv dockerd[2071]: time="2023-05-09T17:59:22.847588914+02:00">
May 09 17:59:22 dh-sv dockerd[2071]: time="2023-05-09T17:59:22.897892390+02:00">
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.552157892+02:00">
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.722402475+02:00">
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.779215890+02:00">
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.779355038+02:00">
May 09 17:59:23 dh-sv systemd[1]: Started Docker Application Container Engine.
lines 1-23...skipping...
● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset>
    Drop-In: /etc/systemd/system/docker.service.d
             └─waitAllMounts.conf
     Active: active (running) since Tue 2023-05-09 17:59:23 CEST; 21min ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
   Main PID: 2071 (dockerd)
      Tasks: 13
     Memory: 40.2M
        CPU: 1.048s
     CGroup: /system.slice/docker.service
             └─2071 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/cont>

May 09 17:59:22 dh-sv systemd[1]: Starting Docker Application Container Engine.>
May 09 17:59:22 dh-sv dockerd[2071]: time="2023-05-09T17:59:22.727058133+02:00">
May 09 17:59:22 dh-sv dockerd[2071]: time="2023-05-09T17:59:22.847588914+02:00">
May 09 17:59:22 dh-sv dockerd[2071]: time="2023-05-09T17:59:22.897892390+02:00">
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.552157892+02:00">
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.722402475+02:00">
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.779215890+02:00">
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.779355038+02:00">
May 09 17:59:23 dh-sv systemd[1]: Started Docker Application Container Engine.
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.899936872+02:00">
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-24/24 (END)
● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/docker.service.d
             └─waitAllMounts.conf
     Active: active (running) since Tue 2023-05-09 17:59:23 CEST; 21min ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
   Main PID: 2071 (dockerd)
      Tasks: 13
     Memory: 40.2M
        CPU: 1.048s
     CGroup: /system.slice/docker.service
             └─2071 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

May 09 17:59:22 dh-sv systemd[1]: Starting Docker Application Container Engine...
May 09 17:59:22 dh-sv dockerd[2071]: time="2023-05-09T17:59:22.727058133+02:00" level=info msg="Starting up"
May 09 17:59:22 dh-sv dockerd[2071]: time="2023-05-09T17:59:22.847588914+02:00" level=info msg="[graphdriver] using prior storage drive>
May 09 17:59:22 dh-sv dockerd[2071]: time="2023-05-09T17:59:22.897892390+02:00" level=info msg="Loading containers: start."
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.552157892+02:00" level=info msg="Default bridge (docker0) is assigned wi>
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.722402475+02:00" level=info msg="Loading containers: done."
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.779215890+02:00" level=info msg="Docker daemon" commit=9dbdbd4 graphdriv>
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.779355038+02:00" level=info msg="Daemon has completed initialization"
May 09 17:59:23 dh-sv systemd[1]: Started Docker Application Container Engine.
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.899936872+02:00" level=info msg="API listen on /run/docker.sock"
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-24/24 (END)...skipping...
● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/docker.service.d
             └─waitAllMounts.conf
     Active: active (running) since Tue 2023-05-09 17:59:23 CEST; 21min ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
   Main PID: 2071 (dockerd)
      Tasks: 13
     Memory: 40.2M
        CPU: 1.048s
     CGroup: /system.slice/docker.service
             └─2071 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

May 09 17:59:22 dh-sv systemd[1]: Starting Docker Application Container Engine...
May 09 17:59:22 dh-sv dockerd[2071]: time="2023-05-09T17:59:22.727058133+02:00" level=info msg="Starting up"
May 09 17:59:22 dh-sv dockerd[2071]: time="2023-05-09T17:59:22.847588914+02:00" level=info msg="[graphdriver] using prior storage driver: overlay2"
May 09 17:59:22 dh-sv dockerd[2071]: time="2023-05-09T17:59:22.897892390+02:00" level=info msg="Loading containers: start."
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.552157892+02:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.722402475+02:00" level=info msg="Loading containers: done."
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.779215890+02:00" level=info msg="Docker daemon" commit=9dbdbd4 graphdriver=overlay2 version=23.0.6
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.779355038+02:00" level=info msg="Daemon has completed initialization"
May 09 17:59:23 dh-sv systemd[1]: Started Docker Application Container Engine.
May 09 17:59:23 dh-sv dockerd[2071]: time="2023-05-09T17:59:23.899936872+02:00" level=info msg="API listen on /run/docker.sock"
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~

Display More

Sorion · May 9th 2023

sudo journalctl -xe

Code

May 09 18:14:05 dh-sv autoshutdown[878]: root: INFO: '_ping_range(): 192.168.178.22 is active'
May 09 18:14:05 dh-sv autoshutdown[878]: root: INFO: '_ping_range(): 192.168.178.24 is active'
May 09 18:14:05 dh-sv autoshutdown[878]: root: INFO: '_ping_range(): 192.168.178.32 is active'
May 09 18:14:05 dh-sv autoshutdown[878]: root: INFO: '_ping_range(): 192.168.178.44 is active'
May 09 18:14:05 dh-sv autoshutdown[878]: root: INFO: '_ping_range(): Active IPs found in the specified range -> no shutdown'
May 09 18:14:05 dh-sv autoshutdown[878]: root: INFO: 'main(): Active check failed, 3 cycles until shutdown ...'
May 09 18:14:05 dh-sv autoshutdown[878]: root: INFO: 'main(): Sleep for 300s'
May 09 18:14:36 dh-sv systemd-networkd[391]: enp3s0: Lost carrier
May 09 18:14:36 dh-sv systemd-networkd[391]: enp3s0: DHCP lease lost
May 09 18:14:36 dh-sv kernel: r8169 0000:03:00.0 enp3s0: Link is Down
May 09 18:14:36 dh-sv avahi-daemon[681]: Withdrawing address record for 192.168.178.48 on enp3s0.
May 09 18:14:36 dh-sv avahi-daemon[681]: Leaving mDNS multicast group on interface enp3s0.IPv4 with address 192.168.178.48.
May 09 18:14:36 dh-sv avahi-daemon[681]: Interface enp3s0.IPv4 no longer relevant for mDNS.
May 09 18:14:39 dh-sv kernel: r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx
May 09 18:14:39 dh-sv systemd-networkd[391]: enp3s0: Gained carrier
May 09 18:14:39 dh-sv systemd-networkd[391]: enp3s0: DHCPv4 address 192.168.178.48/24 via 192.168.178.1
May 09 18:14:39 dh-sv avahi-daemon[681]: Joining mDNS multicast group on interface enp3s0.IPv4 with address 192.168.178.48.
May 09 18:14:39 dh-sv avahi-daemon[681]: New relevant interface enp3s0.IPv4 for mDNS.
May 09 18:14:39 dh-sv avahi-daemon[681]: Registering new address record for 192.168.178.48 on enp3s0.IPv4.
May 09 18:15:01 dh-sv CRON[5045]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
May 09 18:15:01 dh-sv CRON[5046]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
May 09 18:15:01 dh-sv CRON[5047]: (root) CMD (/usr/sbin/omv-mkrrdgraph >/dev/null 2>&1)
May 09 18:15:01 dh-sv CRON[5048]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
May 09 18:15:01 dh-sv CRON[5046]: pam_unix(cron:session): session closed for user root
May 09 18:15:03 dh-sv CRON[5045]: pam_unix(cron:session): session closed for user root
May 09 18:16:40 dh-sv sshd[2306]: Received disconnect from 192.168.178.32 port 49202:11: disconnected by user
May 09 18:16:40 dh-sv sshd[2306]: Disconnected from user dh_user 192.168.178.32 port 49202
May 09 18:16:40 dh-sv sshd[2286]: pam_unix(sshd:session): session closed for user dh_user
May 09 18:17:01 dh-sv CRON[5446]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
May 09 18:17:01 dh-sv CRON[5447]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 09 18:17:01 dh-sv postfix/postsuper[5450]: Deleted: 1 message
May 09 18:17:01 dh-sv CRON[5446]: pam_unix(cron:session): session closed for user root
May 09 18:17:21 dh-sv sshd[5495]: Accepted password for dh_user from 192.168.178.32 port 49331 ssh2
May 09 18:17:21 dh-sv sshd[5495]: pam_unix(sshd:session): session opened for user dh_user(uid=1001) by (uid=0)
May 09 18:17:47 dh-sv sudo[5564]:  dh_user : TTY=pts/0 ; PWD=/ ; USER=root ; COMMAND=/usr/bin/systemctl status docker.service
May 09 18:17:47 dh-sv sudo[5564]: pam_unix(sudo:session): session opened for user root(uid=0) by dh_user(uid=1001)
May 09 18:19:02 dh-sv sshd[5517]: Received disconnect from 192.168.178.32 port 49331:11: disconnected by user
May 09 18:19:02 dh-sv sshd[5517]: Disconnected from user dh_user 192.168.178.32 port 49331
May 09 18:19:02 dh-sv sshd[5495]: pam_unix(sshd:session): session closed for user dh_user
May 09 18:19:02 dh-sv sudo[5564]: pam_unix(sudo:session): session closed for user root
May 09 18:19:05 dh-sv autoshutdown[878]: root: INFO: 'main(): ------------------------------------------------------'
May 09 18:19:05 dh-sv autoshutdown[878]: root: INFO: 'main(): New supervision cycle started, checking system activity'
May 09 18:19:05 dh-sv autoshutdown[878]: root: INFO: '_ping_range(): Retrieve list of active IPs for: enp3s0'
May 09 18:19:10 dh-sv autoshutdown[878]: root: INFO: '_ping_range(): 192.168.178.20 is active'
May 09 18:19:10 dh-sv autoshutdown[878]: root: INFO: '_ping_range(): 192.168.178.21 is active'
May 09 18:19:10 dh-sv autoshutdown[878]: root: INFO: '_ping_range(): 192.168.178.22 is active'
May 09 18:19:10 dh-sv autoshutdown[878]: root: INFO: '_ping_range(): 192.168.178.24 is active'
May 09 18:19:10 dh-sv autoshutdown[878]: root: INFO: '_ping_range(): 192.168.178.32 is active'
May 09 18:19:10 dh-sv autoshutdown[878]: root: INFO: '_ping_range(): 192.168.178.44 is active'
May 09 18:19:10 dh-sv autoshutdown[878]: root: INFO: '_ping_range(): Active IPs found in the specified range -> no shutdown'
May 09 18:19:11 dh-sv autoshutdown[878]: root: INFO: 'main(): Active check failed, 3 cycles until shutdown ...'
May 09 18:19:11 dh-sv autoshutdown[878]: root: INFO: 'main(): Sleep for 300s'
May 09 18:20:30 dh-sv sshd[6038]: Accepted password for dh_user from 192.168.178.32 port 49366 ssh2
May 09 18:20:30 dh-sv sshd[6038]: pam_unix(sshd:session): session opened for user dh_user(uid=1001) by (uid=0)
May 09 18:21:06 dh-sv sudo[6149]:  dh_user : TTY=pts/0 ; PWD=/ ; USER=root ; COMMAND=/usr/bin/systemctl status docker.service
May 09 18:21:06 dh-sv sudo[6149]: pam_unix(sudo:session): session opened for user root(uid=0) by dh_user(uid=1001)
May 09 18:22:53 dh-sv sudo[6149]: pam_unix(sudo:session): session closed for user root
May 09 18:24:11 dh-sv autoshutdown[878]: root: INFO: 'main(): ------------------------------------------------------'
May 09 18:24:11 dh-sv autoshutdown[878]: root: INFO: 'main(): New supervision cycle started, checking system activity'
May 09 18:24:11 dh-sv autoshutdown[878]: root: INFO: '_ping_range(): Retrieve list of active IPs for: enp3s0'
May 09 18:24:11 dh-sv sudo[6654]:  dh_user : TTY=pts/0 ; PWD=/ ; USER=root ; COMMAND=/usr/bin/journalctl -xe
May 09 18:24:11 dh-sv sudo[6654]: pam_unix(sudo:session): session opened for user root(uid=0) by dh_user(uid=1001)

Display More

chente · May 9th 2023

I would say that output is correct...

Still failing to start the container?

Sorion · May 9th 2023

Quote from chente

I would say that output is correct...
Still failing to start the container?

yes.

I still recieve the same error as before when checking or starting to launch the container.

Code

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-f42bb887-736b-4ae1-87b4-3a71cff64bec/compose//jellyfin/jellyfin.yml' --env-file '/srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64bec/compose//jellyfin/jellyfin.env' config 2>&1': parsing /srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64bec/compose/jellyfin/jellyfin.yml: yaml: line 11: mapping values are not allowed in this context

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-f42bb887-736b-4ae1-87b4-3a71cff64bec/compose//jellyfin/jellyfin.yml' --env-file '/srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64bec/compose//jellyfin/jellyfin.env' config 2>&1': parsing /srv/dev-disk-by-uuid-f42bb887-736b-4ae1-87b4-3a71cff64bec/compose/jellyfin/jellyfin.yml: yaml: line 11: mapping values are not allowed in this context in /usr/share/openmediavault/engined/rpc/compose.inc:330
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(619): OMVRpcServiceCompose->{closure}('/tmp/bgstatusre...', '/tmp/bgoutputFA...')
#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}

Display More

I will be gone for a little.

I appreciate all the attempts at helping me with this by you guys. Thank you a lot!

chente · May 9th 2023

Quote from Sorion

- TZ=Europe/Berlin

Now the error is on line 11 of the yaml file. If I'm not mistaken, it's that line. Maybe it doesn't correspond to the location of your server? Check it in the GUI in System>Date&Time in the Time zone field.

Soma · May 9th 2023

On the compose plugin, line numbers don't match the lines of the YML.

The error comes from 1 of the volumes which must be wrong

Change PUID on container after the install - Permission issues?

Participate now!

Similar Threads

[HowTo] Nvidia hardware transcoding on OMV in a Plex docker container

Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

Duplicati in docker: cannot browse subfolders when creating backup rule

SyncThing installation through Portainer not accessible via url

newbie container running problem with OMV5+Docker+rpi3

How to install Plex on OMV6 with docker image linuxserver/plex + On the fly transcoding files only in tmpfs (living on RAM not HDD)