New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

enable_ipv6 not recognised from version 3.0 #4958

Closed
asirinelli opened this Issue Jun 25, 2017 · 8 comments

Comments

Projects
None yet
5 participants
@asirinelli

asirinelli commented Jun 25, 2017

It is not possible to have the enable_ipv6 directive in the composer file if version is 3.0 or higher. This is not consistent with the documentation (https://docs.docker.com/compose/compose-file/).

To be more precise, here is the docker-compose.yml file I am trying to run:

version: '2.2'

services:
  app:
    image: busybox
    command: ifconfig
    networks:
      app_net:
        ipv4_address: 172.16.238.10
        ipv6_address: fc00::10

networks:
  app_net:
    driver: bridge
    enable_ipv6: true
    ipam:
      driver: default
      config:
      - subnet: 172.16.238.0/24
      - subnet: fc00::/64

It runs very well with docker-compose up and the ipv6 address is affected to the container.

If I change the compose file to version 3.0, 3.1, 3.2 or 3.3, receive the following error:

$ docker-compose up
ERROR: The Compose file './docker-compose.yml' is invalid because:
networks.app_net value Additional properties are not allowed ('enable_ipv6' was unexpected)

Is this an error in the documentation or in docker-compose?

For information:

$ docker-compose version
docker-compose version 1.14.0, build c7bdf9e
docker-py version: 2.3.0
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.1t  3 May 2016
$ docker version
Client:
 Version:      17.03.1-ce
 API version:  1.27
 Go version:   go1.7.5
 Git commit:   c6d412e
 Built:        Mon Mar 27 17:14:03 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.03.1-ce
 API version:  1.27 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   c6d412e
 Built:        Mon Mar 27 17:14:03 2017
 OS/Arch:      linux/amd64
 Experimental: false
@shin-

This comment has been minimized.

Member

shin- commented Jun 27, 2017

Not a bug. Network configuration in v3 is currently more limited until Swarm mode is able to support more advanced configurations.

@jorhett

This comment has been minimized.

jorhett commented Jul 2, 2017

@shin well then it's a documentation bug, no?

@shin-

This comment has been minimized.

Member

shin- commented Jul 5, 2017

@jorhett It looks like it is, yes! Feel free to create an issue (or even better, submit a PR) on the docs repo!

@valentin2105

This comment has been minimized.

valentin2105 commented Jul 18, 2017

Any question about this,

So it's not possible anymore to use IPv6 with Docker-compose > 2.1 (3, 3.1, 3.2) ?

Why ?

I have a working 2.1 compose with IPv6 setting for each containers who doesn't work anymore on new compose's version.

@shin-

This comment has been minimized.

Member

shin- commented Jul 18, 2017

I explained this in the comment above: #4958 (comment)

Version 3 should be considered a sidegrade of version 2 for the time being (as both will continue to evolve and be maintained for the foreseeable future)

@valentin2105

This comment has been minimized.

valentin2105 commented Jul 18, 2017

Ok, so we can hope a new version which support IPv6 like 2.1 in newer releases ?
Thanks @shin-

@shin-

This comment has been minimized.

Member

shin- commented Jul 18, 2017

Down the line, yes, that is the expectation.

@Project0

This comment has been minimized.

Project0 commented Nov 30, 2017

I understand why 3.x does not provide ipv6 capabilities, but why this ticket has been closed? Does this more depends on docker swarm project? If yes, is there a another ticket to track this issue?
Ipv6 spec is roughly 20 years old and we are still not able to use it without fearing that software will not support it anymore, really?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment