Thank you, removed all the suggested lines, all is ok now
Case closed.
Posts by BebeMischa
-
-
Code
Display Moreservices: jellyfin: container_name: jellyfin entrypoint: - /init environment: - HOME=/root - LANG=en_US.UTF-8 - LANGUAGE=en_US.UTF-8 - LSIO_FIRST_PARTY=true - NVIDIA_DRIVER_CAPABILITIES=compute,video,utility - PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin - PGID=100 - PUID=998 - S6_CMD_WAIT_FOR_SERVICES_MAXTIME=0 - S6_STAGE2_HOOK=/docker-mods - S6_VERBOSITY=1 - TERM=xterm - TZ=Europe/Amsterdam hostname: 03f6c50fb958 image: lscr.io/linuxserver/jellyfin:latest ipc: private labels: com.docker.compose.config-hash: 6a29f80c20ec7f4a9113627ba6cacc22756aa2d29cb31174ea2f23f02bb57afb com.docker.compose.container-number: 1 com.docker.compose.depends_on: "" com.docker.compose.oneoff: False com.docker.compose.project: jelly com.docker.compose.project.config_files: /data/compose/10/docker-compose.yml com.docker.compose.project.working_dir: /data/compose/10 com.docker.compose.service: jellyfin maintainer: thelamer org.opencontainers.image.authors: linuxserver.io org.opencontainers.image.created: 2022-10-28T23:26:40-05:00 org.opencontainers.image.description: "[Jellyfin](https://jellyfin.github.io/)\ \ is a Free Software Media System that puts you in control of managing and\ \ streaming your media. It is an alternative to the proprietary Emby and Plex,\ \ to provide media from a dedicated server to end-user devices via multiple\ \ apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the\ \ .NET Core framework to enable full cross-platform support. There are no\ \ strings attached, no premium licenses or features, and no hidden agendas:\ \ just a team who want to build something better and work together to achieve\ \ it." org.opencontainers.image.documentation: https://docs.linuxserver.io/images/docker-jellyfin org.opencontainers.image.licenses: GPL-3.0-only org.opencontainers.image.ref.name: 2ff50259c5f6f0fed29e8074a36973275512beae org.opencontainers.image.revision: 2ff50259c5f6f0fed29e8074a36973275512beae org.opencontainers.image.source: https://github.com/linuxserver/docker-jellyfin org.opencontainers.image.title: Jellyfin org.opencontainers.image.url: https://github.com/linuxserver/docker-jellyfin/packages org.opencontainers.image.vendor: linuxserver.io logging: driver: json-file options: {} networks: - jelly_default ports: - 1900:1900/udp - 7359:7359/udp - 8096:8096/tcp - 8920:8920/tcp restart: unless-stopped volumes: - /srv/dev-disk-by-uuid-7fa3a94a-4f3c-4484-8df6-d4bacc7bcbfc/Movies:/data/movies - /srv/dev-disk-by-uuid-7fa3a94a-4f3c-4484-8df6-d4bacc7bcbfc/Movies/TVshows:/data/tvshows - /srv/dev-disk-by-uuid-7fa3a94a-4f3c-4484-8df6-d4bacc7bcbfc/Movies/JJJconfig:/config working_dir: / networks: jelly_default: external: trueBut, how can it be suddenly wrong? It was fine all the time...
-
-
NAS diy build
i3-10105F CPU 16 GB RAM
4 data disc
several SMB shares
Jellyfin
Transmission
Qbittorent
Portainer
Upgraded in 20 minutes, no errors reported. Bravo, dear devs!
-
It's like anything and everything.
If you pay peanuts, you get monkeys. But no need to pay diamonds.
Just go the middle way.
There is cheap crap and there is overpriced crap. Somewhere in between, there is, what you need.
-
running OMV for some years now, my system disk uses 13GB, no any heavy maintenance tasks. I just let the system do it's work...
-
I'm starting to be worried if running a NAS server, which is expected to be fail safe, from a USB stick is safe reliable. But that's my thought...
Running it here from an SSD on a x86 platform for 5 years now, no any failure...
If you build a Fiat, don't expect it to be a Ferrari

-
If you can't find the yaml files anymore, you can autocompose them.
-
Be very aware of language now, before screwing up!
Not running
and
Not seeing
are two very different things! I learned that the hard way...
Same goes for
Not accessible
and
Not working
-
This means, you have some stuff to read... And will then find out, that you can still use Portainer, but also may not even need it anymore.
-
The only place, I would see, there is some potential danger, is here, in this window.
In the list of of updates.
If there would be written in capital letters: ATTENTION, BREAKING CHANGE! , I would study more, before click to get them...

That's actually a result of the good work of OMV team. All updates go so seamlessly, no one is afraid of ruining things. See that as a big compliment

-
It's the family, who will first yell at me, when Jellyfin stops working

-
I would like to know what you did to get to this situation. He probably made a mistake, I don't know if it was the order or what, and I would like to know what that mistake is so that no one else does.
Well, I would like to know too. I'm afraid, I can't explain. I started the migration home alone. Exactly at that moment wife and son came home and disrupted me totally with all the daily questions. So I was auto-piloting the work on OMV until I found out, that I took the wrong course somewhere. I can't recall, where.
I should have paused and wait for next quiet moment.
I'm very sorry, I can't provide useful info...

But the good news is, that the recovery did worked out

-
So, if someone still struggles with hidden containers, maybe worth reading:
PostSomewhere I did screw up the new update, need some assist, please...Hello guys and girls,
So I did the last update and find out, that there were some changes with the Extras, Docker, Portainer and such.
I have done some of the described steps, but as I see now, maybe not in the right order or so, and now I'm stuck.
No hurry, everything still works, but the move from Portainer to Compose plugin is not finished and I don't know, how to.
So, I have this:
Running OMV last version.
Running Docker and Compose plugin:
But I don't see my running containers. (They do run, my…I just got it sorted...

-
So, what I have done now:
1. Run the above mentioned command per container
2. Copy the output.
3. Go to Portainer, remove the container
4. Go to the compose - files - create
5. Paste the output
6. Save
7. select that file and click UP
Done. And that repeating for every container.
-
-
Hello guys and girls,
So I did the last update and find out, that there were some changes with the Extras, Docker, Portainer and such.
I have done some of the described steps, but as I see now, maybe not in the right order or so, and now I'm stuck.
No hurry, everything still works, but the move from Portainer to Compose plugin is not finished and I don't know, how to.
So, I have this:
Running OMV last version.
Running Docker and Compose plugin:
But I don't see my running containers. (They do run, my applications are working normally)
Because I probably did uninstall the old Portainer, and now reinstalled it as per instructions (Portainer OMVextras installed using add from example), I have running Portainer, but all the containers are marked Limited.
I can't find a way to get the yaml compose files, so I can finish the move to the Compose plugin.
Can someone, please guide me a bit, so I can finish this move without loosing the running containers and their settings?
Thank you very much in advance

Mischa
P.S. I do have SSH root access, if it is needed.
-
Anyway, I immediately did change my credentials... Everyone should

btw. Plex did inform us with an e-mail about this.
-
It does not hurt, just wanted to know, if it is normal and not some bug. Now I know enough

-
Second that, I had to SSH for manual update/upgrade. From UI it run, but does nothing.