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.
@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.
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.