Corporate 'Enforced sign-in is enabled' policy 407 error solution #2456
Description
Hey peeps,
First off, thank you for this fantastic library! I'm opening this issue to suggest a small documentation improvement that could help users who are on corporate networks with specific Docker policies.
The Problem
On my work machine, our organization has enabled Docker's "Enforced sign-in" feature. This recently caused our tests and tools that rely on docker-java to fail with a 407 authentication error:
Error during callback: com.github.dockerjava.api.exception.DockerException: Status 407: Pull failed due to an unauthenticated request. Enforced sign-in is enabled, which requires pulls to be authenticated. Run `docker login`, or contact your administrators if this is unexpected.
... More error stack traceThis error prevents docker-java from pulling images, as every request requires authentication.
The Solution
I was able to resolve this by creating a Personal Access Token (PAT) from my corporate Docker user account and then creating a properties file at $HOME/.docker-java.properties with the following content:
# $HOME/.docker-java.properties
registry.username=[YOUR_DOCKER_USERNAME]
registry.password=[YOUR_PERSONAL_ACCESS_TOKEN]This successfully authenticated the requests and resolved the issue.
Proposal
While the documentation correctly mentions the use of the $HOME/.docker-java.properties file in the Getting Started Guide, it doesn't explicitly connect this configuration to the "Enforced sign-in" error message.
I believe it would be very helpful to add a note explicitly mentioning that this method is the correct way to solve authentication issues related to Docker's "Enforced sign-in" policy. This small clarification could save future users in similar corporate environments a significant amount of troubleshooting time.