Question about unknown/unknown Tag in ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator Docker Image

[wzy531a]

Component(s)

No response

Describe the issue you're reporting

Hi,

I noticed that the Docker image ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator contains a tag labeled unknown/unknown. Can someone clarify what this tag represents and what its purpose is?

Thank you!

[jaronoff97]

@wzy531a can you link that image? I looked through GHCR and couldn't find it.

[wzy531a]

@wzy531a can you link that image? I looked through GHCR and couldn't find it.

Yes, when I tried to pull the unknown image, Docker indicated that the operating system is not supported. For now, I tried the following:
[root@k8s-master ~]# docker pull ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:main@sha256:bdf756140620a2e71239185c1fc136291d2ea78c65c36ed861cc5c87f65129fb
Output:
ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator@sha256:bdf756140620a2e71239185c1fc136291d2ea78c65c36ed861cc5c87f65129fb: Pulling from open-telemetry/opentelemetry-operator/opentelemetry-operator e00d8f0bad61: Pulling fs layer operating system is not supported

[jaronoff97]

what OS are you using?

[wzy531a]

what OS are you using?

I am using Linux-x64. The 'unknown' tag is provided for systems where the specific OS is not identified. If the system is not Linux, you can try using the 'unknown' tag image.

[jaronoff97]

Im unclear on what the issue you're experiencing is now. Can you share more information, including logs and OS.

[wzy531a]

Im unclear on what the issue you're experiencing is now. Can you share more information, including logs and OS.

I want to know what the meaning of unknown OS/Arch is?
For example, Linux/amd64 corresponds to a Linux system running on a 64 bit AMD architecture, while Linux/arm64 corresponds to a Linux system running on a 64 bit ARM architecture. So, what is unknown

[pavolloffay]

Adding a screenshot that shows the label.

[pavolloffay]

Pull of that image fails

docker pull ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:v0.103.0@sha256:6b18ceb9907b0ebd75cc077409c01e43f03793f12e1fb3a6cd1f9f1f02e3d795                                                                                                      1 ↵ ploffay@fedora
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Trying to pull ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator@sha256:6b18ceb9907b0ebd75cc077409c01e43f03793f12e1fb3a6cd1f9f1f02e3d795...
Getting image source signatures
Copying blob 0b312dbc66f2 done   | 
Error: writing blob: adding layer with blob "sha256:0b312dbc66f244f2a597a51bcda8111564c4561c931df660590a97ff337a2e9d": processing tar file(archive/tar: invalid tar header): exit status 1

[pavolloffay]

Here it is explained why unknown/unknown is shown https://github.com/orgs/community/discussions/45969

[pavolloffay]

@wzy531a would you like to submit a patch for it?