Open johnplanow opened 7 years ago
Just noticed the first "inspect image" and "tag image" with tag latest...
Executing request GET /v1.18/images/repo.int.company.com%3A5002%2Fcom%2Fcompany%2Fservices%2Fmy-api%3Alatest/json HTTP/1.1
Executing request POST /v1.18/images/com%2Fcompany%2Fservices%2Fmy-api%3Alatest/tag?tag=latest&repo=repo.int.company.com%3A5002%2Fcom%2Fcompany%2Fservices%2Fmy-api&force=0 HTTP/1.1
.. get "404 Not found" and "201 Created" responses, respectively.
Unlike the second "inspect image" and "tag image" with tag feature-US12345...
Executing request GET /v1.18/images/repo.int.company.com%3A5002%2Fcom%2Fcompany%2Fservices%2Fmy-api%3Afeature-US12345/json HTTP/1.1
Executing request POST /v1.18/images/com%2Fcompany%2Fservices%2Fmy-api%3Afeature-US12345/tag?tag=feature-US12345&repo=repo.int.company.com%3A5002%2Fcom%2Fcompany%2Fservices%2Fmy-api&force=0 HTTP/1.1
As mentioned above, BOTH of these get "404 Not found" responses.
Any updated on this issue?? I also got same error on a fresh fabric8 setup instance.
Our case was perhaps a bit unique. We have a somewhat complicated Jenkins build using Maven, which is pushing docker images to a Nexus Repository that has a Docker registry plugin. I don't think the concerns raised in this issue were ultimately the source of our problems. We ultimately fixed it by cleaning up the workflow a little bit -- it seemed our issue was due to building and pushing the Docker image in separate Jenkins build phases.
However, I've left this issue open because the series of HTTP requests the plugin is making still seems potentially problematic.
Description
docker:push fails during tagging trying to get a tagged image that doesn't exist yet. See stack trace at the bottom.
At this point, aside from messing with different versions of docker, I'm somewhat at a loss. I would welcome any advice.
Suspecting configuration problems related to tagging, I've tried multiple approaches:
As well as:
The exception is the same in either case.
I enabled maven's debug output (this was with the second configuration above) and saw the following HTTP requests during docker:push..