Beiträge von messier63

  • [HowTo] SnapRAID in OMV

    Zitat von auanasgheps

    Can you please elaborate better? I don't know Tmux.

    My scripting capabilities are limited, but the code is on Github.

    I'm not well versed in linux so my request might be a stretch.

    With tmux you can essentially resume from where you left off in terminal. A good overview is provided here

    Externer Inhalt www.youtube.com
    Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
    Durch die Aktivierung der externen Inhalte erklären Sie sich damit einverstanden, dass personenbezogene Daten an Drittplattformen übermittelt werden. Mehr Informationen dazu haben wir in unserer Datenschutzerklärung zur Verfügung gestellt.


    Your snapraid script works and i run it overnight. The only issue is that sometimes when i wake up in the morning I'm not certain sure of how far along the script is. The only confirmation or status that you get is once the script is complete.

  • "No space left on device" error despite having enough disk space

    Nothing from above seems to indicate a full drive

    Running df - i shows no issues as well as per below

    On windows, creating a folder in any shared folder creates the same error

    forum.openmediavault.org/wsc/index.php?attachment/26349/


    I'd appreciate help with identifying the issue?

  • "No space left on device" error despite having enough disk space

    Hi all,


    As per the subject, i am getting a "No space left on device" error despite having enough disk space


    Below is the output from running df -ha

  • Jellyfin docker container - Access to the path '/etc/resolv.conf' is denied

    Hi all,


    I started docker all over again and things seem to be working so far. I ran an apt-clean via OMV GUI and deleted the docker folder. Also this time around I allowed OMV to create the folder itself rather than doing it via putty previously.

    From below we see that the + is gone from the docker folder.


    Before reinstall

    Code
    drwxr-xr-x   6 root root  4.0K Apr 27 14:01 .
drwxr-xr-x  12 root root  4.0K Apr 20 00:09 ..
-rw-------   1 root root  9.0K Apr 27 00:47 aquota.group
-rw-------   1 root root  8.0K Apr 27 00:47 aquota.user
drwx--x---+ 13 root root  4.0K Apr 27 00:48 docker
drwxrwsr-x   5 root users 4.0K Apr 27 14:15 dockerappdata
drwxr-xr-x   2 root root  4.0K Apr 27 14:04 dockerscripts
drwx------   2 root root   16K Apr 19 22:45 lost+found

    After reinstall

    Code
    drwxr-xr-x  6 root root  4.0K Apr 27 22:36 .
drwxr-xr-x 12 root root  4.0K Apr 20 00:09 ..
-rw-------  1 root root  9.0K Apr 27 00:47 aquota.group
-rw-------  1 root root  8.0K Apr 27 00:47 aquota.user
drwx--x--- 13 root root  4.0K Apr 27 22:36 docker
drwxrwsr-x  3 root users 4.0K Apr 27 22:54 dockerappdata
drwxr-xr-x  2 root root  4.0K Apr 27 14:04 dockerscripts
drwx------  2 root root   16K Apr 19 22:45 lost+found


    Also previously i was asked to run the commands below which should have yielded -rw-r--r-- for /etc/resolv.conf. Now i am getting the same result whilst previoously i was getting -rw-r----- for /etc/resolv.conf.

    Code
    $ docker run --rm -it --entrypoint="/bin/sh" lscr.io/linuxserver/jellyfin
# ls -l /etc/resolv.conf
-rw-r--r-- 1 root root 59 Apr 27 12:17 /etc/resolv.conf
# exit
$

    So in conclusion the issue seems to boil down to permission issues. and in particular the + for the docker folder?

  • Jellyfin docker container - Access to the path '/etc/resolv.conf' is denied

    Zitat von Zoki

    ls lah /srv/dev-disk-by-uuid-7655cb82-5790-4f01-a9a0-42688f930df5 to see, if something is wrong with permissions.

    Just guessing at the moment.

    Code
    drwxr-xr-x   6 root root  4.0K Apr 27 14:01 .
drwxr-xr-x  12 root root  4.0K Apr 20 00:09 ..
-rw-------   1 root root  9.0K Apr 27 00:47 aquota.group
-rw-------   1 root root  8.0K Apr 27 00:47 aquota.user
drwx--x---+ 13 root root  4.0K Apr 27 00:48 docker
drwxrwsr-x   5 root users 4.0K Apr 27 14:15 dockerappdata
drwxr-xr-x   2 root root  4.0K Apr 27 14:04 dockerscripts
drwx------   2 root root   16K Apr 19 22:45 lost+found

    docker directory looks a bit funny, is it ok in terms of permissions? dockerappdata, where container config files are kept, look ok to me?


    Extra info below


    Code
    # file: srv/dev-disk-by-uuid-7655cb82-5790-4f01-a9a0-42688f930df5/docker
# owner: root
# group: root
user::rwx
group::--x
other::---
default:user::rwx
default:group::rw-
default:other::---
    Code
    getfacl: Removing leading '/' from absolute path names
# file: srv/dev-disk-by-uuid-7655cb82-5790-4f01-a9a0-42688f930df5/dockerappdata/
# owner: root
# group: users
# flags: -s-
user::rwx
group::rwx
other::r-x

  • Jellyfin docker container - Access to the path '/etc/resolv.conf' is denied

    Zitat von Zoki

    Did you move the docker root folder to some disk?

    If yes:

    • what file system
    • does the directory have special permissions

    My docker files are on my OS SSD drive which has been partitioned into two volumes; one for OMV the other for docker.

    The partition for docker is nvme0n1p4 259:4 0 100G 0 part /srv/dev-disk-by-uuid-7655cb82-5790-4f01-a9a0-42688f930df5 from below. It


    Code
    nvme0n1
├─nvme0n1p1 vfat        FAT32            C734-6663                               509M     0% /boot/efi
├─nvme0n1p2 ext4        1.0              50f3acc7-ebc6-42f0-9245-0eff87d18623   12.7G    20% /
├─nvme0n1p3 swap        1                033dca22-5645-4359-8b52-8d97bb8a55ae                [SWAP]
└─nvme0n1p4 ext4        1.0              7655cb82-5790-4f01-a9a0-42688f930df5   89.6G     3% /srv/dev-disk-by-uuid-7655cb82-5790-4f01-a9a0-42688f930df5

  • Jellyfin docker container - Access to the path '/etc/resolv.conf' is denied

    Zitat von Agricola

    Soma is right. You need to start with a fresh install of Jellyfin. Since you are using Stacks you need to:

    1. In Portainer stop the Jellyfin container if it is running, and delete it.
    2. Go into images and delete the unused Jellyfin image.
    3. From your Shared folders you need to delete your config folder at dockerappdata/jellyfin.
    4. Adjust your stack. Comment out the lines that Soma mentioned above.
    5. Redeploy in Stacks.

    I've done steps 1 to 5 and same result. I think my installation is completely messed up somehow


    Zitat von Zoki

    messier63 Something is wrong with your docker installation. The problem is not related to the jellyfin image, as the permissions are wrong for the debain contaienr too.


    What are you running OMV / debian on and how did you install docker?

    I'm running;

    OMV Version: 6.0.22-1 (Shaitan)

    Processor: Intel(R) Pentium(R) Gold G7400T

    Kernel: Linux 5.16.0-0.bpo.4-amd64


    To install docker, I used the install option via omv-extras

  • Jellyfin docker container - Access to the path '/etc/resolv.conf' is denied

    Zitat von Soma

    Bring the container down and delete the config folder.


    Launch again the container to recreate the config folder.


    Check the permissions again

    Same result, also rebooted the host after deleting jellyfin folders

    Zitat von Zoki

    Soma I do not think, /etc is bound to /config in the container. In the command I gave above, no volume was binded into the container and resolv.conf hab wrong permissions.


    Something weird must be going on.


    messier63 can you try with a different container:

    Code
    docker run --rm -it debian ls -lah /etc/resolv.conf

    See below, the result is the same as jellyfin.

    Code
    Unable to find image 'debian:latest' locally
latest: Pulling from library/debian
6aefca2dc61d: Pull complete
Digest: sha256:6846593d7d8613e5dcc68c8f7d8b8e3179c7f3397b84a47c5b2ce989ef1075a0
Status: Downloaded newer image for debian:latest
-rw-r----- 1 root root 618 Apr 27 13:24 /etc/resolv.conf

  • Jellyfin docker container - Access to the path '/etc/resolv.conf' is denied

    I've talking to linuxserver in parallel to this thread and the response is as follows


    Zitat

    I have no idea why docker would be creating the resolv.conf with the wrong permissions. The only other reference to it I can find is someone also on OMV with a similar problem but no solution

    So it seems like I'll have to run the chmod 644 command

  • Jellyfin docker container - Access to the path '/etc/resolv.conf' is denied


    I get an unable to connect error on firefox and chrome on my laptop and phone.

    As did as you suggested in commenting out lines 11, 18, 19 and 20 and same result


    See below for output

    Code
    root@OMV:~# docker run --rm -it --entrypoint="/bin/sh" lscr.io/linuxserver/jellyfin
# ls -l /etc/resolv.conf
-rw-r----- 1 root root 618 Apr 27 12:24 /etc/resolv.conf
# exit

    I see that my output is diffferent to yours, what could cause the issue?

  • Jellyfin docker container - Access to the path '/etc/resolv.conf' is denied

    The ssd was me just making an abbreviation which i guess on reflection will just cause confusion.

    The volume mounts are correct so I'll post all my config files exactly as I've set things up


    My docker files are on my OS SSD drive which has been partitioned into two volumes; one for OMV the other for docker.

    The partition for docker is nvme0n1p4 259:4 0 100G 0 part /srv/dev-disk-by-uuid-7655cb82-5790-4f01-a9a0-42688f930df5 from below.

    On nvme0n1p4 there are two folders/directories

    1. docker - for docker installation
    2. dockerappdata - for container data. This folder is a shared folder that i can access via smb

    I created a user called dockermgnr which as the following id details

    Code
    uid=1000(dockermngr) gid=100(users) groups=100(users),1001(applications)

    So for my latest docker.yaml file, i have the following

    I believe the above aligns with your yaml file with the exception that i don't use symlinks and all ports are active

  • Jellyfin docker container - Access to the path '/etc/resolv.conf' is denied

    Zitat von Soma

    Post the output of  docker logs -f jellyfin

    As a bandaid, I went into the container's exec console via portainer and ran the following to give me access to '/etc/resolv.conf'


    Code
    chmod 644 /etc/resolv.conf

    This allowed me to access Jellyfin's webui. However, that means i have to run the same command i redeploy the container.

  • Jellyfin docker container - Access to the path '/etc/resolv.conf' is denied

    Zitat von Soma

    Your volumes are wrong.

    Read the github properly to set them.


    You don't touch the/etc/resolv.conf, that file belongs to the host, NOT the container.

    I can access the webui now. I was making the mistake of running chmod on the /etc/resolv.conf file on OMV itself when i should be doing that command inside docker via jellyfin's Exec Console.


    Is this a regular issue/bug?


    I'll investigate my volume definition. It may be the reason behind the problem I am facing.

  • Jellyfin docker container - Access to the path '/etc/resolv.conf' is denied

    Zitat von Agricola

    What does ls -l /etc/resolv.conf return?

     root@OMV:~# ls -l /etc/resolv.conf

     lrwxrwxrwx 1 root root 32 Apr 18 12:43 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf 


    Any attempt to chown or chmod the file is unsuccessful and leaves the file as posted above.


    Zitat von Agricola

    Something you can do is comment out all the port lines except the first (8096) one. Also comment out the devices section. Then redeploy the stack. See what happens.

    Tried doing this as well and still the same error. I deployed nginx and qbittorrent and they both worked with no issues.

  • Jellyfin docker container - Access to the path '/etc/resolv.conf' is denied

    Zitat von Agricola

    Your PGID is wrong. I'm not sure if it is what is causing your problems, but it might be. I'm not sure what you mean by "applications group" but all of the PGID's I've seen in OMV is in the range 10x. Here are my user and group:

    Code
    $ id wayne
uid=1000(wayne) gid=100(users) groups=100(users),27(sudo),115(ssh),996(openmediavault-webgui),994(docker)

    run id dockermgnr and see what your gid is. I bet it is 100 also.

    You're right, my gid is 100. The "applications" group is a group i created via OMV gui to access various shared folders that contain app (such as docker) data


    I updated the jellyfin stack but the outcome is still the same, no access to the webgui and the same "Access to the path '/etc/resolv.conf' is denied" error.


    root@OMV:~# id dockermngr

    uid=1000(dockermngr) gid=100(users) groups=100(users),1001(applications)