Turns out it is just a fency feature for azure and aws users and not a drop-in replacement for docker-compose. It feels wrong that this subcomand is called compose… wouldn’t cloud be the better fittings subcommand?! Indeed, it does not allow to deploy localy. Use "docker compose -help" for more information about a command. H, -host string Daemon socket(s) to connect to D, -debug Enable debug output in the logs config DIRECTORY Location of the client config files DIRECTORY (defaul t "/home/me/.docker") docker composeĬonvert Converts the compose file to a cloud format (default: cloudformati on) I had to relogin in order for docker compose to work. I have used the cli-plugin “docker app” in the past, which worked as advertised. I would have expected a cli-plugin in my ~/.docker/cli-plugins folder. The binary in /usr/local/bin/docker appears to have precedence over the default binary in /usr/bin/docker. Seems like the new binary wrapps the old binary… Indeed very confusing. Though, the supposed cli-plugin turned out to be an ordinary binary placed in /usr/local/bin/docker, acompanied by symlink from /usr/bin/docker to /usr/local/bin/. It’s also not listed in docker plugin list : I guess everything started with this gist: and two github issues (or vice-versa). I would love it, if the cli-plugin would be a drop-in replacement for docker-compose Didn’t use it so far, so can’t say wether it is or not. If docker (the project/company) would’ve created it from the scratch, it would high likely be written in go, like the rest of the docker components… bashrc or even better by enabling experimental features in /etc/docker/daemon.jsonĭocker app is another one of those cli-plugins:, which is a Cloud Native application packaging framework.ĭocker-compose started as a standalone third party application (initaly called fig) and was incorparated into the docker ecosystem. In order to make it work, experimental features need to be specificly enabled: either temporary on the shell by setting DOCKER_CLI_EXPERIMENTAL=enabled or permanently by adding the same command to your. docker/compose-cli is one of those cli-plugins, once installed its fuctionality will be available as a subcommand to the docker command. It is an experimental feature called cli-plugin. Starting with docker version 19.03.0, it is possible to extend the docker command with subcommands. It has no mention of deploying docker-compose.yml manifests to cloud providers (except Swarm).ĭid Docker just create two products that are all-but-identically named, read the same docker-compose.yml manifest, both come with Docker Desktop, have many of the same CLI subcommands and flags, but whose deployment targets are disjoint sets? That don’t mention their relationship to one another? What the hell is going on here? The docs on the website refer to docker-compose aka docker/compose, but call it Docker Compose. So is docker/compose-cli the successor to docker/compose? It seems it can’t deploy locally? I get an error $ docker compose upĬommand "compose up" not available in current context (default)īesides the documentation built into the CLI, I can find no documentation about docker/compose-cli.
This is an inherently hard problem to Google, so please hit me with links if I missed something (I searched as hard as I could).
0 kommentar(er)
