I think a key difference with Docker Compose is that this is very much static: ‘guix compose import’ creates a Guix System config snippet.
Would Be Nice™ to also hook up the ‘docker-compose.yml’ parser to create containers on-the-fly, managed by a Shepherd instance, in the spirit of Swineherd: https://github.com/BIMSBbioinfo/swineherd
That would more closely match the developer use case, I guess.
Thank you! Yes that would be the next step: having the ability to spawn transient Shepherd services wrapping OCI containers. They'd be gone on reboot but also podman compose does so I believe.
I don't plan to make this part of the guix command for now. But once https://codeberg.org/guix/guix/pulls/6595 , it will be available as a Guix package and once installed guix compose would be available among the other guix commands like system or pack
5 Comments
civodul@toot.aquilenet.fr · 3 pts · 201d
@fishinthecalculator Woow, nice!
I think a key difference with Docker Compose is that this is very much static: ‘guix compose import’ creates a Guix System config snippet.
Would Be Nice™ to also hook up the ‘docker-compose.yml’ parser to create containers on-the-fly, managed by a Shepherd instance, in the spirit of Swineherd:
https://github.com/BIMSBbioinfo/swineherd
That would more closely match the developer use case, I guess.
fishinthecalculator@lemmy.ml · 2 pts · 201d
Thank you! Yes that would be the next step: having the ability to spawn transient Shepherd services wrapping OCI containers. They'd be gone on reboot but also podman compose does so I believe.
frankenswine@lemmy.world · 1 pts · 200d
awesome! are there intentions to mainline this feature to guix proper?
fishinthecalculator@lemmy.ml · 2 pts · 200d
I don't plan to make this part of the guix command for now. But once https://codeberg.org/guix/guix/pulls/6595 , it will be available as a Guix package and once installed
guix composewould be available among the other guix commands likesystemorpackfrankenswine@lemmy.world · 2 pts · 200d
how cool!