Moby Project - a collaborative project for the container ecosystem to assemble container-based systems (by moby)

Moby Alternatives

Similar projects and alternatives to Moby

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 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 2022-11-02.
  • What is Docker ?
    6 projects | | 2 Nov 2022
    Docker builds a high-level API over execution drivers, such as OpenVZ, systemd-nspawn, libvirt-lxc, libvirt, QEMU/KVM, BSD Jails, Solaris Zones, and chroot to run processes with some degree of isolation and repeatability across environments. The default execution driver since release 0.9 is Docker's own libcontainer driver. It's mainly written in Go, and its source code can be found on Github. See Docker's official website for details.
  • Is My Package Reproducible Yet?
    7 projects | | 1 Nov 2022
    > Because of that, "docker version" on arch linux outputs that it was built on the actual day it was built, whenever that was, and each time it's built that string changes. Hence, not reproducible.

    Fwiw, I'm the maintainer of Docker on Arch and this is a bit more complicated.

    Arch doesn't need to care about build time because `pacman` sets `SOURCE_DATE_EPOCH` during package building which is then utilized by the docker build system.

    If you look at the diff from an actual reproduction of the `docker` package (the Debian Reproducible Builds CI is a fuzzer), you will see there is no issues around build time.

    What you do see is some weird differences around `NT_GNU_BUILD_ID` and `GO BUILDID`.

    This is because of `lto`. In Arch we try to build most Go packages with cgo for the purpose of utilizing hardening flags. The issue is that the C code generation in Golang isn't actually reproducible with `lto` enabled.

    One issue is what I submitted here;

    Another issue which I have been trying to debug is why the code snippet located here doesn't reproduce.

    This results in the BUILDID generated and sat by the cgo build process isn't reproducible.

    I could disable lto and all the binary hardening and docker would probably be reproducible, but where is the fun in that :)?

  • A practical approach to structuring Golang applications
    10 projects | | 3 Oct 2022
  • Where is stated that docker engine (not docker desktop) is free for commercial use and big companies?
    2 projects | | 14 Sep 2022
    Docker is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.
    2 projects | | 14 Sep 2022
    The Docker Engine is open source, so you can technically just download it from here: but you probably still need an installer created by Docker or another Container Orchestration application.
  • Old School Linux Administration (My Next Homelab Generation)
    2 projects | | 11 Sep 2022
    So, for context, my experience is limited to trying to get a MariaDB Galera cluster running. Specifically using the Bitnami image. So my issues might not apply to every single stateful app out there. I'm also running all of this on a vsphere in our own data center. Not in the cloud.

    Swarm does not support dependencies between services. See [0]. It also does not support deploying replicas one at a time. See [1] where I'm asking for that support.

    In the case of Galera, you need a master node to be up and running before you add any new nodes. I'm pretty sure that when you're initiating any kind of stateful clustered app, you'd want to start with one node at a time to be safe. You can't do that in Swarm using a replicated service. All replicas start at the same time.

    Using a service per instance might work, but you need to be sure you have storage figured out so that when you update your stack to add a new service to the stack, the initial service will get the data it was initiated with. (Since when you restart a stack to add the new service, the old service will also get restarted. If I'm remembering what I found correctly.)

    Then there's updating services/replicas. You cannot have Swarm kill a service/replica until after the replacement is actually up and running. Which means you'll need to create a new volume every time you need to upgrade, otherwise you'll end up with two instances of your app using the same data.

    To complicate things, as far as I can tell, Swarm doesn't yet support CSI plugins. So you're pretty much stuck with local or nfs storage. If you're using local storage when deploying new replicas/services, you better hope the first replica/service starts up on same node it was on before...

    All that combined means I haven't figured out how I can run a Galera cluster on Swarm. Even if I use a service per instance, updates are going to fail unless I do some deep customization on the Galera image I'm using to make it use unique data directories per startup. Even if I succeed in that, I'll still have to figure out how to clean out old data... I mean, I could manually add a new volume and service, then manually remove the old volume and service for each instance of Galera I'm running. But at the point, why bother with containers?

    Anyway, I'm pretty sure I've done my research and am correct on all of this, but I'd be happy to be proven wrong. Swarm/Portainer/Traefik is a really really nice stack...


  • Docker als nicht-root laufenlassen?
    3 projects | | 8 Sep 2022
    Und wenn man mal in Moby schaut, das "sammel projekt" unter Docker:
  • Portable code vs Docker on macOS
    2 projects | | 31 Aug 2022
    Technically, nothing stops you from building containers without running Docker's Linux VM. After all it's just a file as any other with a known format. I'm not sure though if it's worth the trouble. There are tools for building images other than Docker but I never used any of those and don't know if they are standalone or are wrappers around Docker. buildah is one of them.
  • Is it possible to download images from Docker Hub without installing Docker?
    2 projects | | 24 Aug 2022
  • Frigate container does not auto start
    2 projects | | 27 Jul 2022
    I had a few times where my gitlab container wasn't working correctly (unhealthy) and I used this container to monitor the health and restart the container automatically as soon as it got unhealthy. As I said above, this requires the container to provide a healthcheck. The autoheal dockerhub repo mentions a pull request that the docker run command should be able to handle a health check on its own.
  • A note from our sponsor - SonarLint | 7 Dec 2022
    Up your coding game and discover issues early. SonarLint is a free plugin that helps you find & fix bugs and security issues from the moment you start writing code. Install from your favorite IDE marketplace today. Learn more →


Basic Moby repo stats
7 days ago
Build time-series-based applications quickly and at scale.
InfluxDB is the Time Series Data Platform where developers build real-time applications for analytics, IoT and cloud-native services in less time with less code.