terrymanu commented on issue #36979:
URL:
https://github.com/apache/shardingsphere/issues/36979#issuecomment-3486779335
Hi @knowwen,
Thank you for providing the build logs. I can see this is a different
issue from the original JVM_OPTS problem.
Analysis of the Build Issue
The error you're encountering is a network connectivity issue when Docker
is trying to pull the base image:
[ERROR] Get "https://registry-1.docker.io/v2/": net/http: request canceled
while waiting for connection (Client.Timeout exceeded while awaiting headers)
This is happening at Step 6/11 when Docker is trying to pull
eclipse-temurin:25-jdk from Docker Hub.
Solutions to Try
1. Configure Docker Mirror (Recommended)
If you're in a region with restricted access to Docker Hub, configure a
Docker mirror:
# Create or edit Docker daemon configuration
sudo mkdir -p /etc/docker
sudo tee /etc/docker/daemon.json > /dev/null <<EOF
{
"registry-mirrors": [
"https://docker.mirrors.ustc.edu.cn";,
"https://hub-mirror.c.163.com";,
"https://mirror.baidubce.com";
]
}
EOF
# Restart Docker daemon
sudo systemctl restart docker
2. Retry the Build
Network issues are often temporary, try running the build again:
./mvnw clean package -Pdocker,docker.build -DskipTests
3. Pre-pull the Base Image
Manually pull the base image first:
docker pull eclipse-temurin:25-jdk
Then retry the build.
4. Check Network Connection
Verify your Docker daemon can reach Docker Hub:
docker run --rm hello-world
Next Steps
Once you resolve the Docker build issue, you can test the JVM_OPTS fix we
discussed earlier. The original JVM_OPTS problem and this Docker build issue
are unrelated, so solving the build issue will allow you to test the
memory configuration fix.
Please let me know if any of these solutions work, or if you need further
assistance with the network connectivity issue.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
