docker:stop raises 404 not found after update to 0.28.0
See original GitHub issueDescription
After upgrading from v0.27.2 to v0.28.0 my integration tests fails on goal docker:stop. This is what the Jenkins output says:
[INFO] --- docker-maven-plugin:0.28.0:stop (docker-rm-img) @ backend ---
[ERROR] DOCKER> 404 page not found (Not Found: 404)
Reverting back to 0.27.2 make the unit test work. This happens only with docker version specified here in the footer. On a more recent version of docker (17.05.0-ce API 1.29) it works with both plugin versions.
Info
- d-m-p version : 0.28.0
- Maven version (
mvn -v
) :
Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e; 2014-06-17T15:51:42+02:00)
Maven home: /home/jenkins/jenkinsslave2/tools/hudson.tasks.Maven_MavenInstallation/maven
Java version: 1.8.0_121, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-59-generic", arch: "amd64", family: "unix"
- Docker version :
Client:
Version: 1.11.2
API version: 1.23
Go version: go1.5.4
Git commit: b9f10c9
Built: Wed Jun 1 22:00:43 2016
OS/Arch: linux/amd64
Server:
Version: 1.11.2
API version: 1.23
Go version: go1.5.4
Git commit: b9f10c9
Built: Wed Jun 1 22:00:43 2016
OS/Arch: linux/amd64
- How to reproduce : On a system with docker version 1.11.2 run a simple test with a configured docker maven plugin that stops a container. Switching the plugin version from 0.27.2 to 0.28.0 makes the error show
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:12
Top Results From Across the Web
Docker daemon answers '404 page not found' after update
The problem comes from the fact that docker needlessly (one could argue erroneously) tries to use proxy (if specified by HTTP_PROXY or ...
Read more >Docker install failing in linux with error [Errno 14] HTTPS Error ...
I am using RHEL 7. I fixed it by editing /etc/yum.repos.d/docker-ce.repo. Replacing $releasever with hard-coded 7 works.
Read more >Troubleshoot common issues - Azure Container Instances
Learn how to troubleshoot common issues when your deploy, run, or manage Azure Container Instances.
Read more >Understanding Docker Hub Rate Limiting
ERROR : toomanyrequests: Too Many Requests. OR. You have reached your pull rate limit. You may increase the limit by authenticating and upgrading...
Read more >yum Docker install error Errno 256 Errno 14 HTTPS Error 404
Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs...
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
I found the problem. It seems that the network mode no longer defaults to “bridge” as said in the documentation. With no network mode specified the log returns network mode “default” and fails here:
Adding this within the run tag in pom.xml:
It works
@gsaviane : Could you please file another issue from with more details(like configuration or full pom itself)? As @NateR42 says, this doesn’t seem related to this issue. We can close this one and open a new one for your problem.