this post was submitted on 26 May 2025
106 points (96.5% liked)

Selfhosted

48688 readers
1395 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Given that Watchtower is potentially unmaintained now, this might be a cool alternative?

Screenshot:

Features from their github:

  • Extremely fast. Cup takes full advantage of your CPU and is hightly optimized, resulting in lightning fast speed. On my Raspberry Pi 5, it took 3.7 seconds for 58 images!
  • Supports most registries, including Docker Hub, ghcr.io, Quay, lscr.io and even Gitea (or derivatives)
  • Doesn't exhaust any rate limits. This is the original reason I created Cup. I feel that this feature is especially relevant now with Docker Hub reducing its pull limits for unauthenticated users.
  • Beautiful CLI and web interface for checking on your containers any time.
  • The binary is tiny! At the time of writing it's just 5.4 MB. No more pulling 100+ MB docker images for a such a simple program.
  • JSON output for both the CLI and web interface so you can connect Cup to integrations. It's easy to parse and makes webhooks and pretty dashboards simple to set up!
you are viewing a single comment's thread
view the rest of the comments
[–] zr0 23 points 1 month ago (10 children)

It sucks to migrate to podman if you have been using Docker Compose heavily.

Also, updating is done with

docker compose pull

and

docker compose up -d

every 24h via cronjob

[–] [email protected] 7 points 1 month ago (6 children)

There's a plugin for compose, but podman itself does have some differences here and there. I'm starting to migrate my own stuff as Docker is getting more money hungry. Womder if they'll try to IPO in a few years. Seems like that's what these kinds of companies do after they start to decline from alienating users. Just wish that portainer and docker hadn't killed all the GUIs for docker and swarm was better supported.

The company i work for has also required us to migrate from Docker as the hub and desktop app are no longer totally free. I expect more and more limitations will show up on the free versions as usually is the case with companies like this.

[–] zr0 3 points 1 month ago (2 children)

Yeah I saw that plugin a few years ago and it was not ready for production yet.

I am going a whole different route, but have the same motivation: get rid of docker and improve the security.

I will move from docker compose to Nomad. And I will also not use containers itself anymore. I want/need more security. You can achieve this with MicroVM (Firecracker). However, you would need to build those VM images yourself. But there is a solution to it. Kata-containers. They allow to deploy OCI compliant containers into seperate MicroVM’s. Then you have true isolation from the host kernel, while not losing much of start-up time.

[–] [email protected] 1 points 4 weeks ago (1 children)

What i read here is concerning. Non that i was getting into the swing of drocker .... :-( Is LXC the future then?

[–] zr0 1 points 4 weeks ago

Docker uses LXC. LXC is actually at the core of many container engines.

load more comments (3 replies)
load more comments (6 replies)