SergeyKanzhelev
commented
1 month ago Internal Server Error often indicate the backend issue. In your error log I see that https:///v2/ is listed instead of the full URL.
I think to make progress here you would need to provide the full command you use, the whole log output, and logs with the maximum verbosity you can think of from the container runtime.
I would expect it is either CRI-O or backend issue though, so this may not be the best repo for this issue
kwilczynski
What happened:
When i try to pull a image from my nexus private repository using the command crictl --debug pull, CRIO didnt pull the image and show the error:
DEBU[0000] PullImageRequest: &PullImageRequest{Image:&ImageSpec{Image:,Annotations:map[string]string{},},Auth:nil,SandboxConfig:nil,}
E1002 17:49:13.548119 2819941 remote_image.go:167] "PullImage from image service failed" err="rpc error: code = Unknown desc = pinging container registry : Get \"https:///v2/\": Internal Server Error" image="/:tag"
FATA[0000] pulling image: rpc error: code = Unknown desc = pinging container registry repo-ace.infoacesso.internal.timbrasil.com.br: Get "https:///v2/": Internal Server Error
This error occurs to any image i try to use from that repository and occurs in all machines of the cluster.
What you expected to happen:
The commands download the image succesfully.
How to reproduce it (as minimally and precisely as possible):
-> Set Up a external Nexus docker hosted repository running on RKE2 and build any image. -> Set Up an OpenShift Cluster -> Try to download any image from the nexus private repository using the command crictl pull
Anything else we need to know?:
I have an HML enverionment running openshift too and from that HML cluster, crioctl works normally.
The funny thing is when i try to use the image using podman pull, its works normally, only with crictl this problem occurs, openshift uses crictl to run pod images, so even with podman working normally, my pod will return a crashLoopBackOff error because the crictl didint work.
Environment:
Container runtime or hardware configuration: 3 Master 5 Workers
OS (e.g:
cat /etc/os-release): NAME="Red Hat Enterprise Linux CoreOS" ID="rhcos" ID_LIKE="rhel fedora" VERSION="414.92.202406041802-0" VERSION_ID="4.14" VARIANT="CoreOS" VARIANT_ID=coreos PLATFORM_ID="platform:el9" PRETTY_NAME="Red Hat Enterprise Linux CoreOS 414.92.202406041802-0 (Plow)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:redhat:enterprise_linux:9::coreos" HOME_URL="https://www.redhat.com/" DOCUMENTATION_URL="https://docs.openshift.com/container-platform/4.14/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="OpenShift Container Platform" REDHAT_BUGZILLA_PRODUCT_VERSION="4.14" REDHAT_SUPPORT_PRODUCT="OpenShift Container Platform" REDHAT_SUPPORT_PRODUCT_VERSION="4.14" OPENSHIFT_VERSION="4.14" RHEL_VERSION="9.2" OSTREE_VERSION="414.92.202406041802-0"Kernel (e.g.
uname -a): Linux sneappnwmprd01 5.14.0-284.69.1.el9_2.x86_64 #1 SMP PREEMPT_DYNAMIC Fri May 31 14:47:07 EDT 2024 x86_64 x86_64 x86_64 GNU/LinuxOthers: OpenShift 4.14.29