82
Best way to manage all my services as containers? (lemmy.ca)
submitted 5 months ago by to c/selfhosted@lemmy.world
56 comments fedilink hide all child comments
 

What to people use and recommend for this? I've read a bit about portainer, but I'm still learning - and don't know what the best solutions are.

Today I have a handful of selfhosted services running on my home machine - mostly installed directly, but a couple running as docker containers. As the scale of my selfhosting has grown, I've realized that things would be a lot easier to manage if each service was run as its own container, so that installed services are isolated.

The solution I'm looking for would make it easy (possibly a web UI) for me to monitor, modify, update, and remove containerized services, including networking and storage.

Edit: Also I would only want a FOSS solution.

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

I personally have switched over to Komodo after using portainer for years. Never looking back, I love it. Works perfectly and can do GUI, compose files, and repos for docker. I also have multiple machines running stuff and it let's me fiddle with everything in one UI.

  • permalink
  • fedilink
  • source
  • hideshow 6 child comments
    •
  • [–] 2 points 5 months ago (1 child)

    Ooo that looks nice, I'm using portainer right now, how was the migration?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 5 months ago

    Honestly, not entirely certain I did it right, but it was super easy. I literally spun up Komodo, spun down Portainer without shutting any of the other containers/stacks down, then added the same stacks back through the GUI option into Komodo with the same exact compose/title/env options. It literally just recognized that the containers that were already running on my server were the correct ones and "added" them back to the stack in Komodo. I vaguely remember reading that there is a more "correct" way to do it, but I only read about it after the fact.

  • permalink
  • fedilink
  • source
  • parent
  • [–] [S] 1 point 5 months ago (3 children)

    Cool! What makes you prefer this to portainer?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 5 months ago* (last edited 5 months ago) (2 children)

    I like the fact that there isn't a distinction between the community edition and the business edition. Its all the same thing for Komodo, whereas I felt like Portainer had a bunc hof random things locked away behind the "Business Edition" and that just rubbed me the wrong way. If I'm self hosting something, I feel like I should be able to access all portions of it.

    The GUI is a little different but once you're used to it, I feel like it makes more sense for the most part. It has a nice way to connect other machines, so I can monitor all of the different machines in my network that are hosting things. I also wanted to mess around with some of the automation features, but I haven't had as much time to dick around with that as I would like. I also wanted to start doing stuff from a personal Forgejo, and it was super easy to integrate. (No idea how easy it is on Portainer, as I had already jumped ship at that point)

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