cockpit/kubernetes image not on docker hub any more

[ZrytyADHD]

Hi Itry to day install okd openshift 3.11 and got error deploying registry console.
i got error:
Failed to pull image "docker.io/cockpit/kubernetes:latest": rpc error: code = Unknown desc = repository docker.io/cockpit/kubernetes not found: does not exist or no pull access

so i check this repo and can't find it because i got error 404 page not found.
Can anyone explain what happend. This repo i essential to run openshift properly.

[timbrd]

This is the related issue which is being discussed in the openshift project: https://github.com/openshift/openshift-ansible/issues/12115

The most recent source of the docker image, which @ZrytyADHD is refering to, can be found here: https://github.com/cockpit-project/cockpit/tree/195.6/containers/kubernetes

[ZrytyADHD]

Ok but can you re upload this image to dockerhub ?
I'm asking because openshift generate error during install cheking image avalability and also we cant install registry console properly without it.

[timbrd]

Ok but can you re upload this image to dockerhub ?
I'm asking because openshift generate error during install cheking image avalability and also we cant install registry console properly without it.

I'm not a member of the cockpit team, so I don't have access to their namespace on dockerhub.
Please follow my instructions in the other issue on using my image as a workaround.

[martinpitt]

Hello @ZrytyADHD ! Indeed I cleaned up some ancient unmaintained images on our dockerhub yesterday. The cockpit-kubernetes package got deprecated a year ago, and that included the cockpit/kubernetes image. It didn't get updated in over a year, and we shouldn't leave dead images around on the hub. It's also not really buildable right now, due to changes in Fedora (and Fedora 29 is EOL).

I can hammer on it for a bit to get it to build again, and put it back from the stable branch, so that it at least picks up current packages. However, this will only be a temporary solution.

The bigger question is, how did you get to use that image from dockerhub in the first place? I. e. which documentation refers to it? If you are running RHEL 7, you should use the official registry-console RHEL container image. You can even do this on CentOS 7 without a subscription.

[ZrytyADHD]

Hi,
I;m not using Redhat Openshift. I install OKD Openshift which is free community edition of Openshift .
When it installing is using images from dockerhub. I can skip docker image availability of course during install or specify any other in my inventory file.
I need to know only one thing: This image from redhat repo is compatibile with community edition ? If yes i can use it but as i know redhat like to modify his images a little bit.

[aroute]

My OKD 3.11's registry-console pod is broken as well. How do I fix an already-installed cluster?

[aroute]

@martinpitt it seems OKD 3.11 is using the image. @timbrd's identified solution works but it would help if the original image reference is restored.

[dbiegunski]

Yes please restore the original image.
Your cleanup should be based on how many times it was pulled within the last year and not if it was updated since last year. There's a lot of traffic coming in for that specific image I'm pretty sure.
Restore shouldn't be that hard ? I believe you guys run full backups ? I hope ?

[timbrd]

Restoring a backup should not be necessary. Just build and upload the most recent image.
The source code can be found here: https://github.com/cockpit-project/cockpit/tree/195.6/containers/kubernetes

The code has been removed with the next tag (196). See this commit also.

[martinpitt]

I put it back with an appropriate deprecation warning: https://hub.docker.com/r/cockpit/kubernetes

[martinpitt]

This repo i essential to run openshift properly.

It's not at all in principle. You don't need the cockpit container registry UI to run a workload, everything is available on the command line as well. It may be part of the OKD deployment installation scripts, of course.

[robbrucks]

# docker pull cockpit/kubernetes:latest
Trying to pull repository docker.io/cockpit/kubernetes ...
manifest for docker.io/cockpit/kubernetes:latest not found

[martinpitt]

@robbrucks : Hm, I don't know what to say. I tried it on RHEL 7 with Docker and Fedora with podman, and pulling that image works fine...

[dry4ng]

Getting this error on CentOS7 and MacOS:
docker pull docker.io/cockpit/kubernetes:latest Trying to pull repository docker.io/cockpit/kubernetes ... manifest for docker.io/cockpit/kubernetes:latest not found

[robbrucks]

The latest supported version of Openshift OKD that is available is 3.11, which locks docker to version 1.13.1.

The 1.13.1 version of docker has problems with the tag manifest on the image and gives us the error. Newer versions of docker don't appear to have a problem with the tag.

Essentially anyone wanting to use the cockpit image of docker hub with the supported version of openshift OKD is out of luck.

[timbrd]

The latest supported version of Openshift OKD that is available is 3.11, which locks docker to version 1.13.1.

The 1.13.1 version of docker has problems with the tag manifest on the image and gives us the error. Newer versions of docker don't appear to have a problem with the tag.

Essentially anyone wanting to use the cockpit image of docker hub with the supported version of openshift OKD is out of luck.

Maybe it's not neccessary to use the deprecated image for much longer. Someone just opened a PR on the openshift-ansible repo which replaces the image with the supported one: https://github.com/openshift/openshift-ansible/pull/12122

[miroslawzachar]

Solution for CentOS 7

_1) Remove Docker 1.13.1_

systemctl stop docker
yum remove docker 
yum remove docker-common

_2) Install Docker CE_

yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
yum install docker-ce

cat > /etc/docker/daemon.json <<EOF
{
  "exec-opts": ["native.cgroupdriver=systemd"],
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "100m"
  },
  "storage-driver": "overlay2"
}
EOF

systemctl start docker

:)

[tinu73]

If you are running RHEL 7, you should use the official registry-console RHEL container image. You can even do this on CentOS 7 without a subscription.

With "CentOS Linux release 7.7.1908 (Core)", i had to follow the instructions proposed by user "pepijnschildkamp" here.

My work around is by creating an empty redhat-uep.pem file.

cd /etc/rhsm/ca/
touch redhat-uep.pem

# oc describe pod registry-console-1-mrmvp
Containers:
  registry-console:
    Image:          registry.access.redhat.com/openshift3/registry-console:v3.9

I installed OpenShift Origin v3.9, therefore in your ansible inventory file you have to use the "old" way to reference the image:

openshift_cockpit_deployer_prefix='registry.access.redhat.com/openshift3/'
openshift_cockpit_deployer_basename='registry-console'
openshift_cockpit_deployer_version='3.9'