4 ms·

Well, it is not like I do regression testing by manually trying "the main features" of my applications. I have many hundreds of automated tests. But since my d

• blibble 5y ago
  give it a v6 address in the same way you give it a v4 address?
  • TekMol 5y ago
    You mean something like this: docker run -p 127.0.0.1:80:80 ... But with an IPv6 address? Which address would I use?
    • mgbmtl 5y ago
      If I recall correctly, you can do "docker run -p [::1]:80:80 .." (::1 is the equivalent to 127.0.0.1). Although I don't know at what point that will test your application. I guess it will at least make sure that it can handle IPs such as "::1".
      • TekMol 5y ago
        docker run -p [::1]:80:80 .. And then how do I send a request to the container? I tried like this: wget 'http://[::1]:80' But that gives me "connection refused".
        • blibble 5y ago
          that would suggest your app isn't listening on the v6 address so you are already testing it :)
          • TekMol 5y ago
            I don't think so. I get the same result when I run "ncat -6 -lp 80" inside the container and try to wget from the outside. When I do the wget inside the container, I get "Connecting to [::1]:80... failed: Cannot assign requested address.". As I said, reading around the net about "docker ipv6", it seems Docker is not IPv6 ready out of the box.
            • El_RIDO 5y ago
              That is correct - please first enable ipv6 and assign it a subnet in your /etc/docker/daemon.json, then restart the service. Details at: https://docs.docker.com/config/daemon/ipv6/ https://docs.docker.com/config/daemon/ipv6/
        • eb0la 5y ago
          I used to type ::1:9092 to connect to my Kafka brokers on my laptop. Best shortcut ever.
• TimWolla 5y ago
  You can assign a Unique Local Address [1] subnet to Docker. Unique Local Addresses are the IPv6 equivalent of 192.168/16, 10/8, ... Docker's documentation explains how to assign an IPv6 subnet to Docker: https://docs.docker.com/config/daemon/ipv6/ https://docs.docker.com/config/daemon/ipv6/ and https://docs.docker.com/network/bridge/#use-ipv6 https://docs.docker.com/network/bridge/#use-ipv6 You then can lookup a container's IPv6 address using 'docker inspect' and then directly connect to it from your host. [1] https://en.wikipedia.org/wiki/Unique_local_address https://en.wikipedia.org/wiki/Unique_local_address
  • TekMol 5y ago
    Docker's documentation Yes, I looked at it and that is what I referred to with "No easy feat".
• El_RIDO 5y ago
  Start by enabling IPv6 on your docker daemon: https://docs.docker.com/config/daemon/ipv6/ https://docs.docker.com/config/daemon/ipv6/ I assume your scenario is that you don't currently use IPv6, so you probably can't assign a subnet of your /48 block of IPv6 range to be routed to your docker host. You can probably use a subnet from a reserved range in that case, for example from: https://en.wikipedia.org/wiki/Unique_local_address https://en.wikipedia.org/wiki/Unique_local_address With that new subnet set up, you would at least be able to test the services running inside containers from that host itself. In my own experience I never encountered services that don't work with IPv6 at all, but as others mentioned the most common issues are with truncated addresses in a db column designed for IPv4 or log parsers that refuse to match on IPv6. Worst case I found was a log based rate limiter that ignored IPv6 addresses and therefore let all requests using that stack pass.