You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
means replacing the docker source with ali? for example, modified file that /etc/docker/damon.json? If that's the case, I recommend using
"registry-mirrors": [
"https://docker.m.daocloud.io"
]
Thanks @g0715158 for the report. From the thread, the build succeeded once you switched the Docker registry mirror, so the failure was caused by access to the registry from your network rather than by the Pulsar build. Also, the Maven docker/pulsar-all build no longer exists: master builds with Gradle (#25398), and the connectors and the pulsar-all image moved to https://github.com/apache/pulsar-connectors (#25408). I'm closing this. If building the image fails on a currently supported release (4.0.x, 4.2.x or 5.0.x) with working registry access, please reopen with the full build output.
Activity
Shuimo03 commentedon Sep 4, 2023
Thisissues looks challenging, is there a rush? If not, can I give it a try?
g0715158 commentedon Sep 5, 2023
Ok. Thank you.
My temporary solution is to change the source to Ali source
Shuimo03 commentedon Sep 5, 2023
means replacing the docker source with ali? for example, modified file that /etc/docker/damon.json? If that's the case, I recommend using
"registry-mirrors": [
"https://docker.m.daocloud.io"
]
github-actions commentedon Oct 6, 2023
The issue had no activity for 30 days, mark with Stale label.
merlimat commentedon Oct 24, 2026
Thanks @g0715158 for the report. From the thread, the build succeeded once you switched the Docker registry mirror, so the failure was caused by access to the registry from your network rather than by the Pulsar build. Also, the Maven
docker/pulsar-allbuild no longer exists: master builds with Gradle (#25398), and the connectors and thepulsar-allimage moved to https://github.com/apache/pulsar-connectors (#25408). I'm closing this. If building the image fails on a currently supported release (4.0.x, 4.2.x or 5.0.x) with working registry access, please reopen with the full build output.