September 10, 2018 8:36 AM, "Alexander von Gluck IV" <kallisti5@xxxxxxxxxxx>
September 10, 2018 8:29 AM, "Alexander von Gluck IV" <kallisti5@xxxxxxxxxxx>
September 10, 2018 8:07 AM, "Alexander von Gluck IV" <kallisti5@xxxxxxxxxxx>
August 31, 2018 3:31 PM, "Andrew Lindesay" <apl@xxxxxxxxxxxxxx> wrote:
I have just deployed 1.0.104 with three notable changes;
* another refresh of the dependencies / build-tooling
* implementation of mirrors
* Docker deployment
Diver just noticed that haikudepotserver isn't updating (even after a
I noticed the "meta URL" for the haikuports repos are still the old vmrepo
ones... could that be
haikudepotserver_1 | Caused by: java.net.NoRouteToHostException: No route to
So, I forgot about a huge gotcha here. Containers can't access public
services shared by other
containers on the same host.
Generally, we use the "internal" url of the resource and things work fine...
but would that
throw off the linkage of haikudepot -> haikudepotserver?
"internal url" means:
These URL's are a bit of a mess since it was decided to host the artifacts
And Java hates the docker internal hostnames... great.
haikudepotserver_1 | java.lang.IllegalStateException: Could not create URI
character in hostname at index 18:
Any workaround for this?