Skip to content
This repository has been archived by the owner on Jun 16, 2021. It is now read-only.

Libcompose 1.0.0 <-> Compose 1.6.0 features #124

Closed
vdemeester opened this issue Dec 24, 2015 · 4 comments
Closed

Libcompose 1.0.0 <-> Compose 1.6.0 features #124

vdemeester opened this issue Dec 24, 2015 · 4 comments
Assignees
Labels

Comments

@vdemeester
Copy link
Collaborator

vdemeester commented Dec 24, 2015

I've tried to come up with a feature grid / missing feature recap' in order to know what to do to achieve a complete compatibility with docker-compose ; and thus making it easy to follow afterwards.

The goal of this issue is to keep track of what is done and what's not. As it might be a little big, we'll probably split this up into small issues for each missing part.

I've created a 1.0.0 milestone (with a cool name I think 😝) to start having some goals and helping us to focus. I also want to follow the releases of the other docker projects (but that's another story).

Anyway, this is what I've got so far. Note there is some stuff that are present in libcompose but not in docker-compose.

ping @docker/libcompose-maintainers @ibuildthecloud @imikushin for feedback.
I probably missed some stuff so, let me know 😉.


Composefile

Reference (v1)

Reference (v2)

To support 👼

CLI

Commands & flags

Commands

Global flags

  • -f, --file FILE
  • -p, --project-name NAME
  • --x-networking
  • --x-network-driver
  • --verbose is also --debug on libcompose-cli
  • -v, --version
  • TLS related flags (--tls, --tlsverify, --tlscacert,
    --tlscert, --tlskey) : how it is handled in docker-compose (compose#1569)
  • --configdir
  • --help, -h should move to help only ?
  • --version, -v should move to version only

Environment Variables

  • COMPOSE_PROJECT_NAME
  • COMPOSE_FILE
  • COMPOSE_API_VERSION
  • DOCKER_* (DOCKER_HOST, DOCKER_TLS_VERIFY,
    DOCKER_CERT_PATH, COMPOSE_HTTP_TIMEOUT)

Miscellaneous

Maybe

Those are in discussion / review on docker-compose so as long as they are not merged or completely sure to get in 1.6.0, it probably shouldn't be in 1.0.0 of libcompose. I'll create issues to track them down.

@vdemeester vdemeester added this to the 1.0.0 Dreamy Schwartz milestone Dec 24, 2015
@vdemeester vdemeester self-assigned this Dec 24, 2015
@vdemeester vdemeester changed the title Compose 1.6.0 features Libcompose 1.0.0 <-> Compose 1.6.0 features Dec 24, 2015
@ibuildthecloud
Copy link
Contributor

@vdemeester Wow, thanks, this is really helpful. I'll look over it more next year (next week 😄 )

@vdemeester
Copy link
Collaborator Author

I still have to list some stuff that would be in the 1.6.0 milestone for docker-compose, see https://github.com/docker/compose/milestones/1.6.0.

And there is also the test-acceptance tests, imported from docker-compose that should help 😉.

@F21
Copy link
Contributor

F21 commented Mar 21, 2016

The --x-networking flag is now removed. Networks are now automatically created by default: https://docs.docker.com/compose/networking/

@vdemeester
Copy link
Collaborator Author

@F21 Thanks :-) I need to close this issue and split it up to be able to follow the gap and progress better ;-)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants