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

test: update fedora toolbox image #14175

Merged

Conversation

giuseppe
Copy link
Member

f32 is already EOL. Let's use the latest version.

Signed-off-by: Giuseppe Scrivano [email protected]

Does this PR introduce a user-facing change?

None

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 10, 2022
Copy link
Collaborator

@flouthoc flouthoc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -14,7 +14,7 @@ var (
BB = "quay.io/libpod/busybox:latest"
healthcheck = "quay.io/libpod/alpine_healthcheck:latest"
ImageCacheDir = "/tmp/podman/imagecachedir"
fedoraToolbox = "registry.fedoraproject.org/f32/fedora-toolbox:latest"
fedoraToolbox = "registry.fedoraproject.org/fedora-toolbox:latest"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am afraid of using a latest tag outside of our control. Can we pin it to a version?

@edsantiago WDYT?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You already know what I think, and you said it :-)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the alternatives seem worse to me though:

[f29/fedora-toolbox](https://registry.fedoraproject.org/repo/f29%2Ffedora-toolbox/tags)
[docker pull registry.fedoraproject.org/f29/fedora-toolbox](https://registry.fedoraproject.org/repo/f29%2Ffedora-toolbox/tags)
[f30/fedora-toolbox](https://registry.fedoraproject.org/repo/f30%2Ffedora-toolbox/tags)
[docker pull registry.fedoraproject.org/f30/fedora-toolbox](https://registry.fedoraproject.org/repo/f30%2Ffedora-toolbox/tags)
[f31/fedora-toolbox](https://registry.fedoraproject.org/repo/f31%2Ffedora-toolbox/tags)
[docker pull registry.fedoraproject.org/f31/fedora-toolbox](https://registry.fedoraproject.org/repo/f31%2Ffedora-toolbox/tags)
[f32/fedora-toolbox](https://registry.fedoraproject.org/repo/f32%2Ffedora-toolbox/tags)
[docker pull registry.fedoraproject.org/f32/fedora-toolbox](https://registry.fedoraproject.org/repo/f32%2Ffedora-toolbox/tags)
[f33/fedora-toolbox](https://registry.fedoraproject.org/repo/f33%2Ffedora-toolbox/tags)
[docker pull registry.fedoraproject.org/f33/fedora-toolbox](https://registry.fedoraproject.org/repo/f33%2Ffedora-toolbox/tags)
[f34/fedora-toolbox](https://registry.fedoraproject.org/repo/f34%2Ffedora-toolbox/tags)
[docker pull registry.fedoraproject.org/f34/fedora-toolbox](https://registry.fedoraproject.org/repo/f34%2Ffedora-toolbox/tags)
[fedora-toolbox](https://registry.fedoraproject.org/repo/fedora-toolbox/tags)
[docker pull registry.fedoraproject.org/fedora-toolbox](https://registry.fedoraproject.org/repo/fedora-toolbox/tags)

Not sure what is the status of that image, but it doesn't even provide a F35 version. F34 will be EOL in one week.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@HarryMichal, git indicates you added that image with commit a1e1a3a. Can you give us guidance on which image we should use?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@HarryMichal, git indicates you added that image with commit a1e1a3a. Can you give us guidance on which image we should use?

The proposed change is correct and you can replace the latest tag with a number that matches a released Fedora version. So a safe choice now would be registry.fedoraproject.org/fedora-toolbox:35 or even registry.fedoraproject.org/fedora-toolbox:36 but probably a bit more stable-ish version is desired here.

The background behind the change can be found in containers/toolbox#615.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for the explanation.

Switched to fedora-toolbox:36

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @HarryMichal !

@vrothberg
Copy link
Member

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 11, 2022
f32 is already EOL.  Let's use the latest version.

Signed-off-by: Giuseppe Scrivano <[email protected]>
@giuseppe giuseppe force-pushed the update-toolbox-image branch from b29aa35 to 6025892 Compare May 11, 2022 18:44
@giuseppe
Copy link
Member Author

ready for review

Copy link
Collaborator

@flouthoc flouthoc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 12, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: flouthoc, giuseppe

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@vrothberg
Copy link
Member

/lgtm
/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 12, 2022
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 12, 2022
@openshift-merge-robot openshift-merge-robot merged commit 1a99a28 into containers:main May 12, 2022
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants