Stop vibe-debugging. Every exception, every backtrace, grouped so you see patterns, not noise. Learn more →
Moby Alternatives
Similar projects and alternatives to Moby
-
-
AppSignal
AppSignal knows why the f*#k it crashed. Stop vibe-debugging. Every exception, every backtrace, grouped so you see patterns, not noise.
-
-
-
-
terraform
Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
-
-
bitwarden_rs
Discontinued Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs [Moved to: https://github.com/dani-garcia/vaultwarden]
-
-
-
-
-
Lean and Mean Docker containers
Slim(toolkit): Don't change anything in your container image and minify it by up to 30x (and for compiled languages even more) making it secure too! (free and open source)
-
nerdctl
contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...
-
CPM.cmake
📦 CMake's missing package manager. A small CMake script for setup-free, cross-platform, reproducible dependency management.
-
Packer
Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
NOTE:
The number of mentions on this list indicates mentions on common posts plus user suggested alternatives.
Hence, a higher number means a better Moby alternative or higher similarity.
Moby discussion
Moby reviews and mentions
Posts with mentions or reviews of Moby.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2026-08-06.
-
A failing Docker swarm service cut healthy containers off the overlay network
TL;DR: On a Docker swarm node, the overlay driver keeps a count of how many endpoints have joined each network there, and destroys the network's sandbox on that node when the count reaches zero. When a container start fails after the driver's Join (for example because the host port it publishes is taken), libnetwork rolls the join back by calling Leave twice, so every such failure takes one more off the count than it added. On Docker 29.8.2, a node with two healthy containers on an overlay network lost that network within 20 seconds of creating a swarm service that published a host port another container already held. Nobody touched anything: the service's own retries did it. Both containers went NO-CARRIER, could no longer reach anything on the overlay, and docker ps showed them running throughout. Restarting the containers didn't bring them back. Restarting the daemon did. The toolkit's check-overlay-sandbox.sh finds containers in that state. Upstream report: moby/moby#53834.
-
Nothing Changed, Except One Kernel Module
dockerd wrote those rules. This host runs Docker Engine 29.6.0, and since Docker Engine 28.0 (2025) — a deliberate hardening change, not a bug — dockerd drops unsolicited inbound traffic to a container's internal IP by default unless the port is explicitly published. The raw-table rules from the previous section are that change's implementation. The blog post doesn't get me that far on its own — it frames the change around unpublished ports and never names a table. What names it is moby#49621, which added DOCKER_INSECURE_NO_IPTABLES_RAW=1 as an opt-out for kernels built without CONFIG_IP_NF_RAW: an escape hatch that only makes sense if the rules were going into raw in the first place.
-
Running FreeIPA on Ubuntu Using Podman
There were many attempts to fix this issue by changing cgroup isolation settings using flags like --cgroupns=host etc ,but nothing worked. Similar outcomes were also obtained by other attempts like these. https://github.com/moby/moby/issues/16238
-
The Definitive Guide to multi-cluster with Pulumi and Docker 25: Lessons Learned
⭐ moby/moby — 71,528 stars, 18,931 forks
- Docker 29 has changed its default image store for new installs
- Thoughts on Go vs. Rust vs. Zig
-
Have you ever run Robocopy on Linux?
The client.Client exposed by the Docker Module provides you with a handle to interact.
-
Announcing udwall: A New Tool for Making UFW and Docker Play Nice With Each Other
GitHub Issues: The original thread moby/moby#4737 is legendary in the Docker community for its longevity.
-
"Your" vs. "My" in user interfaces
> Do you want to delete this? This action is IRREVERSIBLE
Every so often, I’ll check this github issue[0] from 2017, which requests that the various prune commands for docker (e.g. “docker image prune”) have a dry-run flag to display what will actually be deleted. These commands have a warning that data may be deleted, which requires user confirmation to continue, but don’t actually tell you what actions will be performed based on that confirmation until after the deletion has been performed.
[0] https://github.com/moby/moby/issues/30623
- Compiling Docker in RISC-V
-
A note from our sponsor - AppSignal
www.appsignal.com | 7 Oct 2026
Stats
Basic Moby repo stats
251
72,145
10.0
4 days ago
moby/moby is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of Moby is Go.
Sponsored
AppSignal knows why the f*#k it crashed.
Stop vibe-debugging. Every exception, every backtrace, grouped so you see patterns, not noise.
www.appsignal.com