docker.container.<alias>.ip property is no longer set
See original GitHub issueDescription
We recently attempted to upgrade from d-m-p 0.27.2 to 0.30.0, but noticed a regression in our build. It seems that the docker.container.<alias>.ip
is no longer set?
I suspect this is caused by https://github.com/fabric8io/docker-maven-plugin/pull/1130 in 0.28.0. This PR changed the code location where the container properties are exposed. Perhaps they are exposed before the container IP has been assigned?
Info
- d-m-p version : 0.30.0
- Maven version (
mvn -v
) : 3.6.0 - Docker version : 1.12.6
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Container networking - Docker Documentation
By default, the container is assigned an IP address for every Docker network it connects to. The IP address is assigned from the...
Read more >container ip #198 - fabric8io/docker-maven-plugin - GitHub
Inside pom.xml: with the property "docker.host.address" I can get the IP of the host running docker daemon. with the property "host.port" I ...
Read more >A beginner's guide to networking in Docker | by Uday Hiwarale
This way, you don't have to rely on the IP address or hostname of the container and you can freely use the network...
Read more >From inside of a Docker container, how do I connect to the ...
Even if you have the IP address of the docker host it does not mean you can connect to docker host from within...
Read more >Alias IP ranges | VPC - Google Cloud
Using IP aliasing, you can configure multiple internal IP addresses, representing containers or applications hosted in a VM, without having to define a ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Unfortunately the issue still persists in docker-maven-plugin 0.34.0. Docker 1.12.6 is quite old indeed (early 2017). Something in the changes from 0.27.2 to 0.28.0 must have introduced an incompatibility with that docker version. Given that it works on docker 1.13+ I think this can be considered as a low priority issue. Maybe even just a notice in the https://github.com/fabric8io/docker-maven-plugin#docker-api-support.
I’ll try and see if I can upgrade our docker version. If not, I’ll just stick to using 0.27.2.
Thanks to you both for looking into this.
I downgraded the docker version on the test server to 1.12.6 and now I can reproduce the issue there. So it’s a combination of docker-maven-plugin version and docker version that triggers the problem.