Beiträge von buddelschiff

    Here's the Yml code


    Hello,

    photoprism runs very well, but after a reboot of OMV the container stops. (see the screenshot).

    Every time I have to press the "up" button again to make it work again.


    Here is the message when the container restarts.


    docker-compose up -d ...

    time="2023-07-07T16:22:33+02:00" level=warning msg="cannot expand '~', because the environment lacks HOME"

    Container photoprism-mariadb-1 Running

    Container photoprism-photoprism-1 Created

    Container photoprism-photoprism-1 Starting

    Container photoprism-photoprism-1 Started


    END OF LINE



    Does somebody has any idea?

    I guess thunar is another one of your containers.

    no, I started my Linux partition, also because I could only access the restored data from Linux.

    Now I'm back to windows,


    Changing the access rights has no effect, I'm closing for today - I'm a bit frustrated after 7 hours of OMV. :)


    Thanks for the help.



    This is a security issue. If the user running the container belongs to the root group, it is as if the container was run by root. The same goes for the adm group. Why did you do that?

    You're right, no idea why, I changed it.


    uid=1000(myname) gid=100(users) Gruppen=100(users),113(ssh)




    Here is the permission from the compose/jellyfin folder.
    It is on the same drive where the container is located next to OMV.


    Thanks for the help but I can't find the mistake, I changed the GID and also moved the config file to the SSD, see new yaml file below.


    root@openmediavault:~# ls -la /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/media

    insgesamt 16

    drwxr-xr-x 4 myname users 4096 6. Jun 11:35 .

    drwxr-xr-x 9 myname users 4096 6. Jun 14:05 ..

    drwxr-xr-x 2 myname users 4096 6. Jun 11:35 Filme

    drwxr-xr-x 2 myname users 4096 6. Jun 11:35 Serien


    root@openmediavault:~# id myname

    uid=1000(myname) gid=100(users) Gruppen=100(users),0(root),4(adm),113(ssh)



    New yaml:


    ---

    # https://hub.docker.com/r/linuxserver/jellyfin

    version: "2.1"

    services:

    jellyfin:

    image: lscr.io/linuxserver/jellyfin:latest

    container_name: jellyfin

    environment:

    - PUID=1000

    - PGID=100

    - TZ=Europe/Berlin

    - JELLYFIN_PublishedServerUrl=192.168.2.9 #optional

    volumes:

    - /srv/dev-disk-by-uuid-ed942d40-5ba0-4008-b1fb-d0ca1b71638d/compose/jellyfin:/config

    - /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/media/Serien:/data/tvshows

    - /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/media/Filme:/data/movies

    ports:

    - 8096:8096

    - 8920:8920 #optional

    - 7359:7359/udp #optional

    - 1900:1900/udp #optional

    restart: unless-stopped

    Hello,


    I have reinstalled OMV and am working with Docker-Compose for the first time.

    Sorry for the question, I can't find the right guide on the web.

    Jellyfine is running, but I suspect an error in the yaml file because I can't find any media in Jellyfine's web gui.


    Can someone help me please




    This is my yaml file:


    ---

    # https://hub.docker.com/r/linuxserver/jellyfin

    version: "2.1"

    services:

    jellyfin:

    image: lscr.io/linuxserver/jellyfin:latest

    container_name: jellyfin

    environment:

    - PUID=1000

    - PGID=1000

    - TZ=Europe/Berlin

    - JELLYFIN_PublishedServerUrl=192.168.2.9 #optional

    volumes:

    - /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/appdata/jellyfin:/config

    - /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/media/Serien:/data/tvshows

    - /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/media/Filme:/data/movies

    ports:

    - 8096:8096

    - 8920:8920 #optional

    - 7359:7359/udp #optional

    - 1900:1900/udp #optional

    restart: unless-stopped



    and this the report, if check in Compose



    Check compose file for errors ...

    name: jellyfin

    services:

    jellyfin:

    container_name: jellyfin

    environment:

    JELLYFIN_PublishedServerUrl: 192.168.2.9

    PGID: "1000"

    PUID: "1000"

    TZ: Europe/Berlin

    image: lscr.io/linuxserver/jellyfin:latest

    networks:

    default: null

    ports:

    - mode: ingress

    target: 8096

    published: "8096"

    protocol: tcp

    - mode: ingress

    target: 8920

    published: "8920"

    protocol: tcp

    - mode: ingress

    target: 7359

    published: "7359"

    protocol: udp

    - mode: ingress

    target: 1900

    published: "1900"

    protocol: udp

    restart: unless-stopped

    volumes:

    - type: bind

    source: /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/appdata/jellyfin

    target: /config

    bind:

    create_host_path: true

    - type: bind

    source: /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/media/Serien

    target: /data/tvshows

    bind:

    create_host_path: true

    - type: bind

    source: /srv/dev-disk-by-uuid-279fcbf3-10df-4ee3-84fb-2d88e2081cbf/media/Filme

    target: /data/movies

    bind:

    create_host_path: true

    networks:

    default:

    name: jellyfin_default


    END OF LINE

    It was an install from a USB stick. The ISO was downloaded from the OMV website.


    It was the second attempt as I didn't get a connection the first time during the installation either.


    The hardware is an Asrock J3455 with Celeron and 8GB RAM, see screenshot.




    I just realized that I can't install an extension at all.


    Here is the output from systemctl:



    root@OMV:~# systemctl status systemd-resolved

    ● systemd-resolved.service - Network Name Resolution

    Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; ven>

    Active: active (running) since Sun 2023-06-04 16:53:41 CEST; 24min ago

    Docs: man:systemd-resolved.service(8)

    man:org.freedesktop.resolve1(5)

    https://www.freedesktop.org/wi…/systemd/writing-network->

    https://www.freedesktop.org/wi…/systemd/writing-resolver>

    Main PID: 492 (systemd-resolve)

    Status: "Processing requests..."

    Tasks: 1 (limit: 9059)

    Memory: 8.8M

    CPU: 166ms

    CGroup: /system.slice/systemd-resolved.service

    └─492 /lib/systemd/systemd-resolved


    Jun 04 16:53:41 OMV systemd[1]: Starting Network Name Resolution...

    Jun 04 16:53:41 OMV systemd-resolved[492]: Positive Trust Anchors:

    Jun 04 16:53:41 OMV systemd-resolved[492]: . IN DS 20326 8 2 e06d44b80b8f1d39a9>

    Jun 04 16:53:41 OMV systemd-resolved[492]: Negative trust anchors: 10.in-addr.a>

    Jun 04 16:53:41 OMV systemd-resolved[492]: Using system hostname 'OMV'.

    Jun 04 16:53:41 OMV systemd[1]: Started Network Name Resolution.

    lines 1-21/21 (END)...skipping...

    ● systemd-resolved.service - Network Name Resolution

    Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; ven>

    Active: active (running) since Sun 2023-06-04 16:53:41 CEST; 24min ago

    Docs: man:systemd-resolved.service(8)

    man:org.freedesktop.resolve1(5)

    https://www.freedesktop.org/wi…/systemd/writing-network->

    https://www.freedesktop.org/wi…/systemd/writing-resolver>

    Main PID: 492 (systemd-resolve)

    Status: "Processing requests..."

    Tasks: 1 (limit: 9059)

    Memory: 8.8M

    CPU: 166ms

    CGroup: /system.slice/systemd-resolved.service

    └─492 /lib/systemd/systemd-resolved


    Jun 04 16:53:41 OMV systemd[1]: Starting Network Name Resolution...

    Jun 04 16:53:41 OMV systemd-resolved[492]: Positive Trust Anchors:

    Jun 04 16:53:41 OMV systemd-resolved[492]: . IN DS 20326 8 2 e06d44b80b8f1d39a9>

    Jun 04 16:53:41 OMV systemd-resolved[492]: Negative trust anchors: 10.in-addr.a>

    Jun 04 16:53:41 OMV systemd-resolved[492]: Using system hostname 'OMV'.

    Jun 04 16:53:41 OMV systemd[1]: Started Network Name Resolution.