7 ms·

Previously Compose did not have a specification, only the implementation, and it was tied to Docker's products. The aim here is to open it up, and let the speci

Previously Compose did not have a specification, only the implementation, and it was tied to Docker's products. The aim here is to open it up, and let the specification evolve in new directions, such as better supporting deployment on Kubernetes, as an example. It is supported with some other implementations but we want to bring these closer together. Compose has a lot of users, and hundreds of thousands of Compose files on GitHub, so we wanted to open up development as much as possible. (I work at Docker)

deleted 7y ago
[deleted]
liveoneggs 7y ago
Does this spec carry forward the v2 stuff into v3 that would otherwise require --compatibility to function without swarm?
- justincormack 7y ago
  So far we have not made changes to the spec, just carried it forward but we definitely want to start cleaning up the v2 v3 mess, and make a single spec work for all platforms. See https://github.com/compose-spec/compose-spec/issues/12 https://github.com/compose-spec/compose-spec/issues/12 and also https://github.com/compose-spec/compose-spec/issues/13 https://github.com/compose-spec/compose-spec/issues/13 for making it feature not version number driven.
  - znpy 7y ago
    <insert python joke here>
  - liveoneggs 7y ago
    I would be surprised if there is the political will at docker to do this when it wasn't a priority for compose itself
    - fapjacks 7y ago
      Docker (Inc) has new priorities and different influences. I'm inclined to feel some optimism that this shifting focus will have beneficial repercussions in places like this.
- geerlingguy 7y ago
  This. My current usage is a muddy mess of v2 and v3 specific features an some require the compatibility flag while others don't.
e12e 7y ago
> better supporting deployment Is there any "supported deployment" for docker? I had the impression that swarm has been sidelined, and docker-compose was discouraged. Is there a path to deployment on kubernetes that uses only compose? (I have a hard time seeing how that'll work with ingress, and "compose" well with other kubernetes deployments?) We have some on-prem stuff that would work on single-node swarm - but I've felt that compose has been in a bit of limbo this past year or so... Is some kind of production style deployment comming back?
- hannibalhorn 7y ago
  "Compose on Kubernetes"[1] seems to be what they're advocating at the moment, and it's included in Docker Desktop. It's probably an OK first step for simpler deployments, though I suspect in order to do any troubleshooting, one would have to learn k8s anyway. 1. https://github.com/docker/compose-on-kubernetes https://github.com/docker/compose-on-kubernetes
  - mfer 7y ago
    To debug an application running on linux one does not need to learn machine code or assembly. There are tools that make it all possible. Higher level abstractions can work and need to start somewhere. It really depends what tools are developed.
    - e12e 7y ago
      Have you tried moving from on-premise docker-compose to managed kubernetes in the cloud? If you've been diligent in striving for stateless containers that will help you - but pretty much everything thing else in your compose file is useless. Docker-compose gets you the "pod"-level in k8s, but doesn't really help with ingress/services etc. So no one can reach your app, certainly not via a load balancer that terminate ssl for you. This is no longer a game of "beating the nginx container until it gives up and does what you need it to".
      - mfer 7y ago
amerine 7y ago
Hi Justin, I work at Heroku for Salesforce. I'm unsure if you've worked with anyone here in the past (like on our older app.yml, heroku.yml and constellations, etc stuff). But I just wanted to say thanks for establishing a standard for this and helping the rest of us in this space continue to evolve.
mcny 7y ago
Hi, I would like to use docker-compose without using docker. Specifically, I’d like to run devil box (php development environment) on fedora using pod man and docker-compose. Is that possible now?
girvo 7y ago
I'm super excited for this. Back when Docker Compose was still called Fig, I got annoyed at how it handled volume-only containers for databases, and wrote Dup [1]. Nowadays Compose is way WAY more useful, but there's a number of projects that still rely on it -- the spec means I can write a converter for the config files (from Dup to Compose) and be sure that it will work :) [1] https://github.com/girvo/dup https://github.com/girvo/dup

deleted 7y ago

[deleted]

liveoneggs 7y ago

Does this spec carry forward the v2 stuff into v3 that would otherwise require --compatibility to function without swarm?

justincormack 7y ago
So far we have not made changes to the spec, just carried it forward but we definitely want to start cleaning up the v2 v3 mess, and make a single spec work for all platforms. See https://github.com/compose-spec/compose-spec/issues/12 https://github.com/compose-spec/compose-spec/issues/12 and also https://github.com/compose-spec/compose-spec/issues/13 https://github.com/compose-spec/compose-spec/issues/13 for making it feature not version number driven.
- znpy 7y ago
  <insert python joke here>
- liveoneggs 7y ago
  I would be surprised if there is the political will at docker to do this when it wasn't a priority for compose itself
  - fapjacks 7y ago
    Docker (Inc) has new priorities and different influences. I'm inclined to feel some optimism that this shifting focus will have beneficial repercussions in places like this.
geerlingguy 7y ago
This. My current usage is a muddy mess of v2 and v3 specific features an some require the compatibility flag while others don't.

e12e 7y ago

> better supporting deployment Is there any "supported deployment" for docker? I had the impression that swarm has been sidelined, and docker-compose was discouraged. Is there a path to deployment on kubernetes that uses only compose? (I have a hard time seeing how that'll work with ingress, and "compose" well with other kubernetes deployments?) We have some on-prem stuff that would work on single-node swarm - but I've felt that compose has been in a bit of limbo this past year or so... Is some kind of production style deployment comming back?

hannibalhorn 7y ago
"Compose on Kubernetes"[1] seems to be what they're advocating at the moment, and it's included in Docker Desktop. It's probably an OK first step for simpler deployments, though I suspect in order to do any troubleshooting, one would have to learn k8s anyway. 1. https://github.com/docker/compose-on-kubernetes https://github.com/docker/compose-on-kubernetes
- mfer 7y ago
  To debug an application running on linux one does not need to learn machine code or assembly. There are tools that make it all possible. Higher level abstractions can work and need to start somewhere. It really depends what tools are developed.
  - e12e 7y ago
    Have you tried moving from on-premise docker-compose to managed kubernetes in the cloud? If you've been diligent in striving for stateless containers that will help you - but pretty much everything thing else in your compose file is useless. Docker-compose gets you the "pod"-level in k8s, but doesn't really help with ingress/services etc. So no one can reach your app, certainly not via a load balancer that terminate ssl for you. This is no longer a game of "beating the nginx container until it gives up and does what you need it to".
    - mfer 7y ago

amerine 7y ago

Hi Justin, I work at Heroku for Salesforce. I'm unsure if you've worked with anyone here in the past (like on our older app.yml, heroku.yml and constellations, etc stuff). But I just wanted to say thanks for establishing a standard for this and helping the rest of us in this space continue to evolve.

mcny 7y ago

Hi, I would like to use docker-compose without using docker. Specifically, I’d like to run devil box (php development environment) on fedora using pod man and docker-compose. Is that possible now?

girvo 7y ago

I'm super excited for this. Back when Docker Compose was still called Fig, I got annoyed at how it handled volume-only containers for databases, and wrote Dup [1]. Nowadays Compose is way WAY more useful, but there's a number of projects that still rely on it -- the spec means I can write a converter for the config files (from Dup to Compose) and be sure that it will work :) [1] https://github.com/girvo/dup https://github.com/girvo/dup