this post was submitted on 26 Oct 2024
540 points (99.5% liked)

Linux

48313 readers
1120 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
540
Jellyfin 10.10.0 media server released (jellyfin.org)
submitted 3 weeks ago by petsoi@discuss.tchncs.de to c/linux@lemmy.ml
73 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] M600@lemmy.world 17 points 3 weeks ago (6 children)

I just setup Jellyfin on docker the other day for the first time.

It just occurred to me that I don’t know how to update docker.

Any advice?

[–] dangling_cat@lemmy.blahaj.zone 25 points 3 weeks ago* (last edited 3 weeks ago) (3 children)

Check out Watchtower! Auto-update your containers. Don’t forget to set WATCHTOWER_CLEANUP to true, or your disk will be filled with old images.

[–] butter@midwest.social 4 points 3 weeks ago

I couldn't figure out watchtower. I just made a script to pull and restart and scheduled it to run daily at midnight.

[–] M600@lemmy.world 2 points 3 weeks ago

Thanks! I’ll check that out, I’m really loving how quick and easy docker has been so far.

[–] KryptonNerd@slrpnk.net 2 points 3 weeks ago

Oh this looks great! Thanks for the suggestion

[–] talentedkiwi@sh.itjust.works 14 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

Did you use docker compose file or just run a command to start the container?

Edit: I always use compose files. For that you can do the following:

docker compose pull
docker compose down
docker compose up -d

You don't technically need the stop, but I've found once or twice in the past where it was good to stop because of image dependencies that I forgot to put in my compose.

For running a command directly I found this website that seems to summarize it pretty well I think:

https://www.cherryservers.com/blog/how-to-update-docker-image

[–] M600@lemmy.world 3 points 3 weeks ago (1 children)

Yes, I used docker compose. Do I need to do anything to clean up with this method?

[–] talentedkiwi@sh.itjust.works 3 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

Now that you mention it, I always do a

docker system prune -f

This will clean up old images that are no longer used. I setup an alias command in Linux to do all of those commands.

I just named it docker_update and saved it in my ~/.bashrc

[–] talentedkiwi@sh.itjust.works 3 points 3 weeks ago (1 children)

I see someone mention watchtower, while not a bad thing, I just prefer to manually update. This helps to ensure any breaking changes don't break my system. Especially with something like Immich at it's had a lot of them recently as they work towards stable. I just generally subscribe to their release and do updates as necessary.

[–] avidamoeba@lemmy.ca 3 points 3 weeks ago

And there are breaking changes in this Jellyfin release.

[–] avidamoeba@lemmy.ca 8 points 3 weeks ago

You could use a systemd unit file:

[Unit]
Description=docker_compose_systemd-sonarr
After=docker.service 
Requires=docker.service

[Service]
TimeoutStartSec=0

WorkingDirectory=/var/lib/sonarr

ExecStartPre=-/usr/bin/docker compose kill --remove-orphans
ExecStartPre=-/usr/bin/docker compose down --remove-orphans
ExecStartPre=-/usr/bin/docker compose rm -f -s -v
ExecStartPre=-/usr/bin/docker compose pull
ExecStart=/usr/bin/docker compose up

Restart=always
RestartSec=30

[Install]
WantedBy=multi-user.target

You'd place your compose file in the working dir /var/lib/sonarr. Depending on what tag you've set for the image in the compose file, it would be autoupdated, or stay fixed. E.g. lscr.io/linuxserver/sonarr:latest would get autoupdated whereas lscr.io/linuxserver/sonarr:4.0.10 would keep the container at version 4.0.10. If you want to update from 4.0.10, you'd have to change it in the compose file.

[–] Quail4789@lemmy.ml 4 points 3 weeks ago

no need for docker compose down. pull && up is enough

[–] CosmicTurtle0@lemmy.dbzer0.com 4 points 3 weeks ago (1 children)

If you set up using compose and don't have the version pinned:

dockee compose down && docker compose pull jellyfin && docker compose up -d

[–] Sandbag@lemm.ee 5 points 3 weeks ago (1 children)

What about if I am using Podman and have the container as a systemd unit file?

[–] exu@feditown.com 3 points 3 weeks ago

Podman supports auto updating natively by setting a label.
I use systemd service files for running containers, but you can add the same label on the command line or in quadlet files.

https://wiki.exu.li/linux/podman#auto-update-container

[–] Tenkard@lemmy.ml 3 points 3 weeks ago

Also depends on how you specified image in the docker. If it has no version or latest as version it will update otherwise it may be fixed