cli

ame, Docker Swarm will use the IP from the first network (sorted lexically) where the service name exists. In a multi-tenant setup, where a lot of services are connected to an ingress network (i.e. Taefik), this may lead to a service connecting to a container from a different network than expected. The only solution is to always append the network name to the service name (e.g. service.customer-network; see [3]). - Due to some reason I still wasn't able to figure out, the cluster will sometimes just break. The leader loses its connection to the other manager nodes, which in turn do NOT elect a new leader. The only solution is to force-recreate the whole cluster and then redeploy all workloads (see [4]). Sure, our use case is somewhat special (running a cluster used by a lot of tenants), and we were able to find workarounds (some more dirty than others) to most of our issues with Docker Swarm. But what annoys me is that for almost all of the issues we had, there was a GitHub ticket that didn't get any official response for years. And in many cases, the reporters just give up waiting and migrate to K8s out of despair or frustration. Just a few quotes from the linked issues: > We, too, started out with Docker Swarm and quickly saw all our production clusters crashing every few days because of this bug. […] This was well over two years (!) ago. This was when I made the hard decision to migrate to K3s. We never looked back. > We recently entirely gave up on Docker Swarm. Our new cluster runs on Kubernetes, and we've written scripts and templates for ourselves to reduce the network-stack management complexities to a manageable level for us. […] In our opinion, Docker Swarm is not a production-ready containerization environment and never will be. […] Years of waiting and hoping have proved fruitless, and we finally had to go to something reliable (albeit harder to deal with). > IMO, Docker Swarm is just not ready for prime-time as an enterprise-grade cluster/container approach. The fact that it is possible to trivially (through no apparent fault of your own) have your management cluster suddenly go brainless is an outrage. And "fixing" the problem by recreating your management cluster is NOT a FIX! It's a forced recreation of your entire enterprise almost from scratch. This should never need to happen. But if you run Docker Swarm long enough, it WILL happen to you. And you WILL plunge into a Hell the scope of which is precisely defined by the size and scope of your containerization empire. In our case, this was half a night in Hell. […] This event was the last straw for us. Moving to Kubernetes. Good luck to you hardy souls staying on Docker Swarm! Sorry, if this seems like like Docker Swarm bashing. K8s has it's own issues, for sure! But at least there is a big community to turn to for help, if things to sideways. [1]: https://github.com/docker/cli/issues/2527 [2]: https://github.com/moby/moby/issues/37338 [3]: https://github.com/docker/compose/issues/8561#issuecomment-1... [4]: https://github.com/moby/moby/issues/34384

e tangible progress before diving back into a long-running project that moves forward in fits and starts. Beyond getting to tackle some bite-sized projects, I'd say the thing that sustains me is getting to work with clients. It's tons of fun when people come to me with a vision that we can iterate on and bring into reality. And then the flip side is also rewarding: getting to scratch an itch and turn a design I've been turning over in my mind into reality. Edited to add: If you've got an idea for a furniture or woodworking project, my contact info and website are in my profile. https://github.com/docker/cli/issues/267#issuecomment-695149...

ability of systems and the developer experience: https://www.youtube.com/watch?v=lFRKrHE8oPo Nowadays, you can actually use something like Typer for Python to create similarly useful interfaces, which i strongly advise you to have a brief look at: https://typer.tiangolo.com/ Example: $ docker Usage: docker [OPTIONS] COMMAND A self-sufficient runtime for containers Options: ... (a list of items) -v, --version Print version information and quit Management Commands: ... (a list of items) image Manage images Commands: ... (a list of items) Run 'docker COMMAND --help' for more information on a command. To get more help with docker, check out our guides at https://docs.docker.com/go/guides/ $ docker image Usage: docker image COMMAND Manage images Commands: ... (a list of items) ls List images ... (a list of items) pull Pull an image or a repository from a registry Run 'docker image COMMAND --help' for more information on a command. $ docker image pull "docker image pull" requires exactly 1 argument. See 'docker image pull --help'. Usage: docker image pull [OPTIONS] NAME[:TAG|@DIGEST] Pull an image or a repository from a registry $ docker image pull alpine:3.15 3.15: Pulling from library/alpine 59bf1c3509f3: Pull complete Digest: sha256:21a3deaa0d32a8057914f36584b5288d2e5ecc984380bc0118285c70fa8c9300 Status: Downloaded newer image for alpine:3.15 docker.io/library/alpine:3.15 $ docker image ls REPOSITORY TAG IMAGE ID CREATED SIZE alpine 3.15 c059bfaa849c 11 hours ago 5.59MB The worst: tar Why: https://xkcd.com/1168/ In short, it's the exact opposite of the previous example. Frankly, without memorizing the flags, i still have no idea how to work with archives with it. Say, i want to create a compressed archive with it. Example: $ tar tar: You must specify one of the '-Acdtrux', '--delete' or '--test-label' options Try 'tar --help' or 'tar --usage' for more information. $ tar --usage Usage: tar [-AcdrtuxGnSkUWOmpsMBiajJzZhPlRvwo?] [-g FILE] [-C DIR] [-T FILE] [-X FILE] [-f ARCHIVE] [-F NAME] [-L NUMBER] [-b BLOCKS] [-H FORMAT] [-V TEXT] [-I PROG] [-K MEMBER-NAME] [-N DATE-OR-FILE] ... (a really long list of items) $ tar --help Usage: tar [OPTION...] [FILE]... GNU 'tar' saves many files together into a single tape or disk archive, and can restore individual files from the archive. Examples: tar -cf archive.tar foo bar # Create archive.tar from files foo and bar. tar -tvf archive.tar # List all files in archive.tar verbosely. tar -xf archive.tar # Extract all files from archive.tar. Main operation mode: ... (a list of items) -c, --create create a new archive Operation modifiers: ... (a list of items) Local file name selection: ... (a list of items) File name matching options (affect both exclude and include patterns): ... (a list of items) Overwrite control: ... (a list of items) Select output stream: ... (a list of items) Handling of file attributes: ... (a list of items) Handling of extended file attributes: ... (a list of items) Device selection and switching: ... (a list of items) -f, --file=ARCHIVE use archive file or device ARCHIVE Device blocking: ... (a list of items) Archive format selection: ... (a list of items) FORMAT is one of the following: ... (a list of items) Compression options: ... (a list of items) -z, --gzip, --gunzip, --ungzip filter the archive through gzip Local file selection: ... (a list of items) File name transformations: ... (a list of items) Informative output: ... (a list of items) -v, --verbose verbosely list files processed Compatibility options: ... (a list of items) Other options: ... (a list of items) Mandatory or optional arguments to long options are also mandatory or optional for any corresponding short options. The backup suffix is '~', unless set with --suffix or SIMPLE_BACKUP_SUFFIX. The version control may be set with --backup or VERSION_CONTROL, values are: ... (a list of items) Valid arguments for the --quoting-style option are: ... (a list of items) *This* tar defaults to: --format=gnu -f- -b20 --quoting-style=escape --rmt-command=/usr/lib/tar/rmt.exe --rsh-command=/usr/bin/rsh $ # Copied from the Internet, because the documentation is overwhelming $ tar -vczf new-archive.tar.gz ./files-i-want-to-archive ./files-i-want-to-archive/ ./files-i-want-to-archive/test1.txt ./files-i-want-to-archive/test2.txt ./files-i-want-to-archive/test3.txt $ # Consider the full format instead, maybe we should actually use the full parameters more often? $ tar --verbose --create --gzip --file=new-archive.tar.gz ./files-i-want-to-archive In short, using tar does not inspire joy and it feels overcomplicated, no matter how you look at it, possibly either because creating archives is a complicated domain (though the zip tool might not necessarily support that claim), or because the tool has grown over time and no longer does just one thing and does it well.