17
Container vs service (lemmy.world)
submitted 2 years ago* (last edited 2 years ago) by to c/jellyfin@lemmy.ml
16 comments fedilink hide all child comments
 

The last post on the subject I could find was a year ago. So thought I would ask again. I have debian 12 up on miniPC and I have my NAS mounted. My intention is to use jellyfin and some of the arr* stuff. I know only a little about systemd (I just google what I need to know). I have some contianer knowledge, but mostly in k8s. And the docker parts aren't really my problem. But I have a vague understanding of docker. What are the latest pros and cons of containers vs service installation?

Edit: The opinions were unanimous. Containers it is.

you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 2 years ago (2 children)

Cannot recommend container approach enough. The learning curve isn't too bad, initially it can be daunting but best way is to jump straight in and try it.

Few things I recommend:

  • Portainer, a very nice container management webapp
  • Use compose /stack from day 1, or at least try it before you get carried away with too many containers. Take a copy and save somewhere and build up your catalogue of containers/configs.
  • Volumes, make sure they are persistent.
  • Backup your docker config folders, especially if using development branches.
  • Spend a day/weekend playing with setup, expecting to throw away and start again. Sounds bad but it's not. If you use compose/stacks you can spin up in seconds.
  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] 4 points 2 years ago

    Please use Dockge instead of Portainer.

    Dockge makes it much easier to actually see what's happening in the deployment process and debug any issues, instead of presenting the error on a small popup that vanishes after 0.3 seconds, and it gives you much better feedback when you misconfigure something in your compose file. It also makes it much easier to interact with your setup from the command line once you feel comfortable doing that. And the builtin docker run to docker compose feature is really handy.

    Newbies will find Dockge much friendlier, and experienced users will find that it respects their processes and gets out of the way when you want it out of the way.

  • permalink
  • fedilink
  • source
  • parent
  • [–] [S] 1 point 2 years ago (1 child)

    When you say "Backup your docker config folders". Are you talking about the directory were you would store the dockerfile / docker compose file?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 years ago (1 child)

    That too, but no, I was referring to the data/config folders for each container.

    For example, radarr it would be the config volume you mounted. Generally, the *arrs use a volume called 'config', but other containers will differ.

    I've only had to recover from backups twice in 5 years, once was my fault after fiddling with databases. But if you're using the development/nightly branches, it's best to be cautious and avoid having to reconfigure.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •