Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build and publish multi-arch image manifest #98

Closed
jbpratt opened this issue Dec 23, 2021 · 5 comments · Fixed by kubevirt/project-infra#2240
Closed

build and publish multi-arch image manifest #98

jbpratt opened this issue Dec 23, 2021 · 5 comments · Fixed by kubevirt/project-infra#2240
Labels
kind/enhancement lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@jbpratt
Copy link

jbpratt commented Dec 23, 2021

/kind enhancement

What happened:
Installing on a RPi cluster, the container will fail to start

What you expected to happen:
A container to become ready :)

How to reproduce it (as minimally and precisely as possible):
Provision an arm64 cluster and install

  • Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"archive", BuildDate:"2021-11-18T21:20:32Z", GoVersion:"go1.17.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.6", GitCommit:"d921bc6d1810da51177fbd0ed61dc811c5228097", GitTreeState:"clean", BuildDate:"2021-10-27T17:44:26Z", GoVersion:"go1.16.9", Compiler:"gc", Platform:"linux/amd64"}
  • Cloud provider or hardware configuration: arm64 RPi4 cluster (really a mixed arch cluster)

KubeVirt hostpath-provisioner 'manifest'

❯ podman manifest inspect quay.io/kubevirt/hostpath-provisioner:v0.9.0
WARN[0000] Warning! The manifest type application/vnd.docker.distribution.manifest.v2+json is not a manifest list but a single image.
{
    "schemaVersion": 2,
    "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
    "config": {
        "mediaType": "application/vnd.docker.container.image.v1+json",
        "size": 1941,
        "digest": "sha256:598bd51ee3fe65884755944a2752dba4699d7b3a45ba59e51dbadfddd34b4403"
    },
    "layers": [
        {
            "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
            "size": 40936435,
            "digest": "sha256:8bf48c4f2db7d0909f8e1bd3cfdbcace7ad3d11bcf7bd971709e01bfc284a67a"
        },
        {
            "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
            "size": 17835264,
            "digest": "sha256:04bb4d0cf6e1ec4183666590405650097f1826cc97b928ec526fa63d29c5407d"
        }
    ]
}

Rancher local-path-provisioner manifest

❯ podman manifest inspect docker.io/rancher/local-path-provisioner:v0.0.21
{
    "schemaVersion": 2,
    "mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
    "manifests": [
        {
            "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
            "size": 739,
            "digest": "sha256:cf7422ac6e9bc9a5cb9ae913bdc8b0f20db8db6f5b77ea5a6446338ea3acd8fc",
            "platform": {
                "architecture": "amd64",
                "os": "linux"
            }
        },
        {
            "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
            "size": 739,
            "digest": "sha256:239ed0c6c28dcb217088f4e52b9759bad1dd44e9bdd5a9cf3d655cb7a2a950de",
            "platform": {
                "architecture": "arm64",
                "os": "linux"
            }
        },
        {
            "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
            "size": 739,
            "digest": "sha256:42f79a6523c49b68e0445c2552c29b1a58c220ead8fba5b3acf4beb12778e379",
            "platform": {
                "architecture": "arm",
                "os": "linux"
            }
        },
        {
            "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
            "size": 739,
            "digest": "sha256:82a4f1a459ac41d27a97a14e1a0694cc158a922461c4d932761da4475080c7c3",
            "platform": {
                "architecture": "s390x",
                "os": "linux"
            }
        }
    ]
}
@kubevirt-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 23, 2022
@jbpratt
Copy link
Author

jbpratt commented Mar 23, 2022

/remove-lifecycle stale

@kubevirt-bot kubevirt-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 23, 2022
@kubevirt-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 21, 2022
@jbpratt
Copy link
Author

jbpratt commented Jun 21, 2022

/remove-lifecycle stale

@kubevirt-bot kubevirt-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 21, 2022
@awels
Copy link
Member

awels commented Jun 22, 2022

/lifecycle frozen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants