You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason why docker-compose is broken because it was explicitly built against
glibc and CargOS is using musl libc.
The official docker-compose binaries will only run with glibc.
We are looking at the issue and will provide a working docker-compose package
in the next couple of days.
@rnagy thank you for the fast reply, actually after I have faced that issue, I've looked for some alternatives, and found rancherOS. Seems like cargOS and rancherOS both, are using busybox under the hood.
I found, that the installation process of cargOS is a bit nicer, because it has that wizard which lets you set up the system and so on. On the other hand, rancherOS can be configured with a simple yml file, which is also very nice, because you can commit, store, share that configuration and deploy to a bunch of nodes if you like.
However, could you describe what the main difference between these two host systems are?
By following the steps to install a package, I installed
docker-compose
ls -la /usr/pkg/bin/docker-compose
showed that the binary existsBut
$ docker-compose up
returned the error message:/usr/pkg/bin/docker-compose: no such file or directory
The text was updated successfully, but these errors were encountered: