4 ms·
Does this spec carry forward the v2 stuff into v3 that would otherwise require --compatibility to function without swarm?
by liveoneggs 7y ago
Does this spec carry forward the v2 stuff into v3 that would otherwise require --compatibility to function without swarm?
- justincormack 7y agoSo 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 agoI 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 agoDocker (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 agoThis. My current usage is a muddy mess of v2 and v3 specific features an some require the compatibility flag while others don't.