Dockerfmt: A Dockerfile Formatter
github.com
Dockerfmt: A Dockerfile Formatter
1–10 of 67 posts
Re: Dockerfmt: A Dockerfile Formatter
#2Re: Dockerfmt: A Dockerfile Formatter
#3Side question. Why would people continue to build new dockerfiles as opposed to using Podman ?
Dockerfiles is the language for specifying a set of instructions for building container images.
Re: Dockerfmt: A Dockerfile Formatter
#4Re: Dockerfmt: A Dockerfile Formatter
#5Side question. Why would people continue to build new dockerfiles as opposed to using Podman ?
Re: Dockerfmt: A Dockerfile Formatter
#6Side question. Why would people continue to build new dockerfiles as opposed to using Podman ?
Re: Dockerfmt: A Dockerfile Formatter
#7I just use a yaml LSP which will probably try to lookup the schema.org Containerfile format for this. I first noticed this recently when working on a Github Actions yaml file. Pretty nifty.
Re: Dockerfmt: A Dockerfile Formatter
#8Re: Dockerfmt: A Dockerfile Formatter
#9Side question. Why would people continue to build new dockerfiles as opposed to using Podman ?
Podman uses Dockerfiles too. Dockerfiles is the language for specifying a set of instructions for building container images.
# syntax=docker/dockerfile:1
I suspect that the GP was really asking "why not use a different tool", like buildah https://buildah.io>, buildpacks https://buildpacks.io>, nix https://nix.dev/tutorials/nixos/building-and-running-docker-...>,
kaniko https://github.com/GoogleContainerTools/kaniko>, ko https://github.com/ko-build/ko>, bazel https://github.com/bazel-contrib/rules_oci>, apko https://github.com/chainguard-dev/apko>, or other tools.Each of those has tradeoffs compared to Dockerfiles (I have no need for bazel, but if I did, then adding `rules_oci` might be a win-win, rather than using a Dockerfile). If I used Nix, then the Nix dockerTools would be a huge win (I don't use Nix). If I were shipping Go programs, `ko` would likely be a good baseline.