[haiku-depot-web] Re: Update : Mirrors / Dependency / Docker

  • From: "Alexander von Gluck IV" <kallisti5@xxxxxxxxxxx>
  • To: apl@xxxxxxxxxxxxxx, haiku-depot-web@xxxxxxxxxxxxx
  • Date: Mon, 10 Sep 2018 14:03:06 +0000

September 10, 2018 8:36 AM, "Alexander von Gluck IV" <kallisti5@xxxxxxxxxxx> 
wrote:

September 10, 2018 8:29 AM, "Alexander von Gluck IV" <kallisti5@xxxxxxxxxxx> 
wrote:

September 10, 2018 8:07 AM, "Alexander von Gluck IV" <kallisti5@xxxxxxxxxxx> 
wrote:

August 31, 2018 3:31 PM, "Andrew Lindesay" <apl@xxxxxxxxxxxxxx> wrote:

Hello;

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 
manual trigger)

https://build.haiku-os.org/buildmaster/master/x86_64/?buildrunDir=1998
https://eu.hpkg.haiku-os.org/haikuports/master/x86_64/current/packages/uhexen2-1.5.9-1-x86_64.hpkg

I noticed the "meta URL" for the haikuports repos are still the old vmrepo 
ones... could that be
the cause?

Ack.. no:

haikudepotserver_1 | Caused by: java.net.NoRouteToHostException: No route to 
host (Host
unreachable)

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:

http://buildmaster_frontend_1:80/haikuports/repository/master/x86_64/current/
http://buildmaster_frontend_1:80/haikuports/repository/master/x86_gcc2/current/

These URL's are a bit of a mess since it was decided to host the artifacts 
from buildmaster
directly.

And Java hates the docker internal hostnames... great.

haikudepotserver_1 | java.lang.IllegalStateException: Could not create URI 
object: Illegal
character in hostname at index 18:
http://buildmaster_frontend_1:80/haikuports/repository/master/x86_gcc2/current/repo.info

Any workaround for this?

Ok.. Solved.  I created an alias for buildmaster_frontend_1 called 
"buildmaster" and adjusted the repos.


http://buildmaster:80/haikuports/repository/master/x86_64/current
http://buildmaster:80/haikuports/repository/master/x86_gcc2/current

seems to be working (and the "virtual name" solver should fix it when clients 
lookup their repo.


 -- Alex

Other related posts: