cli VS cli

I am a self-employed furniture maker. I'm that guy who somewhat infamously no longer builds software[0]. About a year ago I moved my operations from a makerspace to my own shop. That's come with its ups and downs.

On the one hand, I know which idiot last used a tool: me.

On the other, I would no longer see other humans besides my wife most weeks. To keep sane I also work one day a week at a bike shop fixing bikes. It's something I'd done on a volunteer basis many years back.

The unexpected nice thing about this is that it gives me projects that are an hour or two in size in addition to the many-week sized projects that I do as part of my business. It's sort of like getting to fix a small bug in the midst of adding a big feature; it lets me pop out of the big project for a bit and see something else through from start to finish and see some 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.

https://github.com/docker/cli/issues/267#issuecomment-695149...

Furniture making

On the topic of alternatives I use https://fishshell.com/ and have the Docker Completions installed.

More cases like this (but don't seem to have a consensus): https://github.com/docker/cli/issues/2686

anything happening with this that anyone is aware of: https://github.com/docker/cli/issues/2802

I found a few different issues in docker tracker about this issue, but the only one which seems to be merged is this one which has docker ignore any options which start with x- but that doesn't seem to help here as the local log driver then just complains about:

The service in the error is about docker swarm (that you didn't mention). It seems like you have an issue similar to this one: https://github.com/docker/cli/issues/2875

Docker itself is open-source, and has slowly been broken down into modular components that are themselves open-source. For example, most of what "run this Docker container" does has been extracted out into containerd, which is Apache licensed and used by lots of things. The Docker CE engine is now based on Moby, also Apache license, and the docker command line tool is also Apache licensed. I expect these tools to continue to be community-maintained (though maybe without the Docker name) due to their immense popularity even Docker Inc folds.

Docker has a bunch of components, including the CLI, a runtime etc. They're pretty much all definitely open source, e.g.: https://github.com/docker/cli

GitHub CLI - GitHub on the command line. Great for creating PRs, etc.

This package is widely used for powerful CLI builds, it is used for example for Kubernetes CLI and GitHub CLI, in addition to offering some cool features such as automatic completion of shell, automatic recognition of flags (the tags) , and you can use -h or -help for example, among other facilities.

This Docker image is designed to support implementing Github Actions with Python. As of version 4.0.0., it starts with the official python docker image as the base which is a Debian OS. It specifically uses python:3-slim to keep the image size down for faster loading of Github Actions that use pyaction. On top of the base, we've installed curl gpg, git, and the GitHub CLI. We added curl and gpg because they are needed to install the GitHub CLI, and they may come in handy anyway (especially curl) when implementing a GitHub Action.

You might be interested in GitHub's cli tool, which is open source, if you want to access GitHub without running their proprietary JS code.

https://cli.github.com/

👉 Note: This script uses the GitHub CLI. So make sure you've installed that if you haven't already. Instructions here.

View on GitHub

(Context: I'm pretty thick into Nix, and have been for about four years. Most of this post is focussed on the NixOS desktop experience, so DevOps nerds, ymmv.)

Unpopular opinion: Nix is not that hard.

What's "hard" from a nix-promotion strategy is motivating people to understand why they would want the benefits it offers. Mostly because Nix, especially with home-manager, dramatically worsens UX for several day-to-day tasks, simply by violating the Law of Least Surprise every couple of hours in normal use.

I want a fully idempotent, version-locked, rewindable user environment, with a version-controlled central config, because I have half a dozen devices that, for reasons, I need to keep perfectly interchangeable with one another. Most users do not want this, for the simple fact that mutating their configs and differentiating them locally on specific machines is not a bug, but a feature.

Even more than that, it's an expectation that most software developers share as well.

Case in point: I filed a bug against the GitHub CLI last week. If any org has the scope and motivation to build software that's compatible with NixOS, an OS most of whose users are developers, it should be GitHub, which is, at least notionally, all about developers, developers, developers. A change in GH required a config format migration, which was sensibly done by opening the config .yml and rewriting it.

Of course, this breaks NixOS not just in practice but in principle. NixOS/home-manager makes config files read-only. Surprise! https://github.com/cli/cli/issues/8462

The response from GitHub was basically, "yeah, we knew this was going to happen, we mentioned it to the packagers at NixOS, but we did it anyway, because it was still the best way to proceed for us." (And they weren't wrong.)

Now, once a month is an annoyance, but I run into these problems daily. I can't imagine any sane person -- which I am not -- would persist with using it.

Why do I keep using NixOS, then? Because I am terribly and disproprotionately annoyed by small changes in my user experience, which I find disruptive to my workflow and hence threaten my success. For me, forbidding apps from mutating the config files I established for them is a selling point. Being able to version-control an idempotent declarative config for all of them at once is heaven.

Unless you're like me, you'll hate NixOS. But some were meant for Nix.

Because

To use a proper dynamic auth for ghcr.io you can create a "credential helper" and then it is supported by flux, see here: https://fluxcd.io/flux/cheatsheets/oci-artifacts/#authentication Unfortunately the "official" credential helper for ghcr.io doesn't exist. I use this simple script as a helper: https://gist.github.com/pkit/a98411d21ecc9293066f4579088187d1 Which requires gh cli to be installed.

This Docker image is designed to support implementing Github Actions with Python. As of version 4.0.0., it starts with the official python docker image as the base which is a Debian OS. It specifically uses python:3-slim to keep the image size down for faster loading of Github Actions that use pyaction. On top of the base, we've installed curl gpg, git, and the GitHub CLI. We added curl and gpg because they are needed to install the GitHub CLI, and they may come in handy anyway (especially curl) when implementing a GitHub Action.

Two CLI tools I install right away are the GitHub CLI (via brew) and the Netlify CLI (via npm).