Pharos docker registry timeout (504)

[jakubknejzlik]

What happened:

registry.pharos.sh report timeout with status code 504 and docker cannot pull pharos images.

What you expected to happen:

200 status code and successful docker pull.

How to reproduce it (as minimally and precisely as possible):

docker pull registry.pharos.sh/kontenapharos/kube-proxy:v1.14.9

Anything else we need to know?:

Environment:

$ docker version
Client: Docker Engine - Community
 Version:           19.03.5
 API version:       1.40
 Go version:        go1.12.12```

[matti]

registry has been shut down

[jakubknejzlik]

@madddi on purpose?

[matti]

jes @jacub, the company shut down

[jakubknejzlik]

Ah, that's sad news. Would be nice to be informed ahead on some official channel.

Anyway, I'll keep this open as this affects all users interacting with pharos-cluster tool and basically disables the usage of the whole solution (initialization of new cluster and managing the running clusters).

[matti]

well they did publish a blogpost etc almost two months ago

[shinebayar-g]

Kontena is completely shut down. They announced it on their slack channel and website which is shut down now. Unfortunately there isn't any info on github.

[0x4139]

can't we get the image source code and just push them to another repository?

[shinebayar-g]

That won't work. Because pharos cluster is integrated with their services. Authentication etc..

[jakubknejzlik]

@shinebayar-g AFAIK kontena's services are not mandatory for OSS version. We had problems only with downtime of pharos registry.

[0x4139]

if anyone has an kontena version up and running we could extract the tar archives and push them to a new registry

[jakolehm]

All the images are available under docker.io/kontenapharos.

[0x4139]

@jakolehm thank you, do you think they can be open sourced the ones used in pharos? So we can update them as time goes by?

[jakolehm]

There is very little to open source.. most of the stuff is built from upstream sources. Basically most were a build pipeline configs which were used to bake multi-arch images (because upstream was not always providing those).

Pharos 3.x (which is pure OSS) has switched to use upstream repos so this should not be a problem anymore.