2 ms·
There is nothing Go-like about Dockerfiles. The file naming seems to be an offshoot of Heroku's "Procfile" convention. I have no idea where the syntax came from
by yencabulator 2y ago
There is nothing Go-like about Dockerfiles. The file naming seems to be an offshoot of Heroku's "Procfile" convention. I have no idea where the syntax came from, but it's superficially a very simple "SHOUTYCOMMAND arguments...\n" grammar with no structure beyond sequence-of-lines. Perhaps it's the more imperative cousin of the ".env" files popular with web devs.
- benatkin 2y agoI guess it's kind of like assembly where COMMAND foo is like INSTRUCTION foo. Maybe it just clicked for me and I can't think of a syntax I'd prefer for it. Which now has me wondering about modeling syntaxes for other things on it. For some reason it reminded me of the WAC model from WebAssembly component model https://component-model.bytecodealliance.org/creating-and-consuming/composing.html#advanced-composition-with-the-wac-language https://component-model.bytecodealliance.org/creating-and-co... No particular comparison, but I'd like to understand how constructing a container image might compare to constructing a wasm module from components.