Thank you all for the help. I was worried that it was a resolution problem if the package name or version had changed. It is very clearly now an issue with my network, not the source or Maven.
Sent with Proton Mail secure email. On Friday, August 22nd, 2025 at 5:03 PM, Robert Devitt <[email protected]> wrote: > Sometimes docker networking can be funny. > > What is the output of `docker run maven:3-eclipse-temurin-21 curl > https://repo.maven.apache.org/maven2` ? Might help to isolate the issue. > > On Fri, Aug 22, 2025 at 1:52 PM Nick Couchman [email protected] wrote: > > > On Fri, Aug 22, 2025 at 4:29 PM viktor_krumm <[email protected] > > .invalid> > > wrote: > > > > > Both curl and openssl s_client work just fine. I can connect to Maven. > > > I > > > am wondering if there is an upstream change in the dependency or path for > > > some reason. I believe the Dockerfile was compiling right earlier today. > > > > I don't think an upstream dependency change would cause the error you're > > seeing - it very clearly says: > > > > Network is unreachable > > > > This isn't an issue with Maven not being able to find a dependency that's > > changed or something like that, it's saying that it cannot connect to the > > server. > > > > Perhaps it's just a transient issue, and will go away on its own - maybe > > the Maven repo is throttling traffic or something like that? > > > > -Nick > > > > -- > Robert Devitt > [email protected] [email protected]
