composerize VS yq

composerize.com sounds like a useful tool to start - I had that precise problem yesterday. I could only find run commands for something, which I've been avoiding.

To confirm you have the right docker-compose.yml structure, you can paste your run command in Composerize and copy and paste the output into your yml file. It helps considerably when migrating over from Docker Run. Docker Run is a great way to start with Docker, but Docker Compose is the best way to keep it running cleanly and more consistently. Best of luck!

I'm trying to generate a compose file and am having a hard time with the "--gpus all" section. What I've been able to find isn't working and composerize.com doesn't seem to handle it at all as it just ignores it in the generated file. I'm not sure exactly how to format it's addition to my compose file.

There's composerize you can make use of.

This seems to definitely be the consensus! Someone on twitter linked me to a tool called Composerize which seems to be able to generate docker-compose configs directly from a docker run command which is exactly what I need.

It's really just a docker-run wrapper yes. I find it much easier to edit / keep track of my settings, but it's a personal preference probably. For my multi-container scenarios that daisy-chain it's much much easier (for me anyway). And not all containers have docker-compose.yaml examples, so you'd want to know about "composerize.com".

Compserize

Just follow the links on the site: https://github.com/magicmark/composerize

What I often use to just get the full key paths is yq (https://github.com/mikefarah/yq), piping into grep when necessary

  yq -o=props 

For more information about this command visit https://github.com/mikefarah/yq

I've been trying to install and config a plugin (papis.nvim) for a couple of days and am having issues with a function that uses io.popen to run yq to convert yaml files to json. I know my install of yq is fine- I can run yq -oj info.yaml from the command line with no issue and it produces the correct json output. I know the function can find the yq executable, but it returns nil. I've saved the error from the yq golang code: panic: runtime error: invalid memory address or nil pointer dereference

- yq has no if-then-else https://github.com/mikefarah/yq/issues/95 which is a poor design (or omission) in my opinion

After which, I use openapi-generator to make a yaml output.

https://gist.github.com/freshteapot/3637e8d2b5ecdf01b7d25246...

- yq version 3.4.1 (Worth noting, the example uses an out of date yq, so a few modifictaions might be needed)

https://github.com/mikefarah/yq

For those pining for a similar yaml query tool for working through acres of config: https://github.com/mikefarah/yq

jq is awesome and thanks to the new team for their recent efforts and energy, it massively appreciated.

For anyone looking for such a script, there's some CLIs that make it easy. One is `yq -o props` [1], another way is to use `yq -j` or `yj` [2] to convert to JSON and pipe it to `gron` [3].

[1] https://github.com/mikefarah/yq

[2] https://github.com/sclevine/yj

[3] https://github.com/tomnomnom/gron