Compose: Support IPAM gateway in version 3.x

[rvernica]

Is your feature request related to a problem? Please describe.

See #6555

Describe the solution you'd like

The documentation page sis it all:

Note: Additional IPAM configurations, such as gateway, are only honored for version 2 at the moment.

I would be nice to have a more complete support of IPAM/network in the compose file for version 3.x.

Describe alternatives you've considered

I've considered downgrading to version 2.x but it seems a step backward.

[cjsimon]

Also see https://github.com/docker/compose/issues/4474

[bastiao]

Any possible alternatives with v3?
This is weird because the default gateway is set as X.Y.Z.1.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically marked as not stale anymore due to the recent activity.

[kewur]

just stumbled upon this. official ecs documentation were using gateway so I had to revert back to version 2.

https://aws.amazon.com/blogs/compute/a-guide-to-locally-testing-containers-with-amazon-ecs-local-endpoints-and-docker-compose/

[smgoller]

Would definitely like to be using version 3 files. What needs to be done to make this supported?

[EricHripko]

Releases 1.27.0+ have merged v2/v3 file formats, so you should be able to use ipam anywhere now.

[roelvanduijnhoven]

@EricHripko That would be great! However the docs still tell me the following:

Additional IPAM configurations, such as gateway, are only honored for version 2 at the moment.
-- https://docs.docker.com/compose/compose-file/#ipam

Do you think the docs are outdated in this regards?

[EricHripko]

Yep - I don't think the docs have been updated to reflect the changes introduced by _1.27.0+_ yet.

[PrplHaz4]

Yep - I don't think the docs have been updated to reflect the changes introduced by _1.27.0+_ yet.

What is the minimum 3.x docker-compose file version this will be supported in? Will anything 3.0+ be valid (in addition to 2.0+) as it's just a docker-compose update, not a spec bump?

[EricHripko]

_1.27.0+_ drops the requirement for version attribute (so you don't even have to specify it any more). This indeed means that you can mix any 3.0+ features with any 2.0+ features 🙂