Open ginkel opened 5 years ago
Do you have the same behaviour when you a do a plain docker confluentinc/cp-schema-registry:latest
? I'm asking because the actual contact to the registry happens by the Docker daemon, not d-m-p. So if you get the same error with plain docker usage, then there is not much d-m-p can do here.
Also the JSON error message looks like as that comes directly from the Docker daemon or registry.
Description
When attempting to pull a Docker image not yet present from Docker Hub d=m=p mails with a error 400:
Complete stacktrace:
The image is referenced from a
docker-compose.yml
file:POM excerpt:
Info
mvn -v
) : Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T20:41:47+02:00)