the most common complaint i see people have with Docker is the quip "it works on my machine => i'll ship my machine" but this is literally the _least_ of the issues with Docker

every new thing i learn about Docker and container infrastructure as a whole is somehow more upsetting than the previous one. the entire thing is bad. OCI is bad. none of it is well-designed, most of it makes barely any sense at all, hardly any can be reasonably run at scale

why is `buildah rm` and `buildah remove` two completely unrelated commands. does nobody involved give a shit about UI design

quick! tell me which of `docker export` and `docker save` operates on images and which on containers

why is everything like this!!

@whitequark at least it doesn’t have both --dryrun and --dry-run that turn off different parts of actually doing the thing
@rfc6919 i'm sorry what

@whitequark

semgrep

--dry-run
When set, will not start a scan on semgrep.dev and will not report
findings. Instead will print out json objects it would have sent.

--dryrun
If --dryrun, does not write autofixes to a file. This will print
the changes to the console. This lets you see the changes before
you commit to them. Only works with the --autofix flag. Otherwise
does nothing.

@rfc6919 How do you un-read a Mastodon post? This needs a CW for cognitohazard
@krans largely how i felt when i worked out why my dry run wasn’t doing what i expected