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.

Sign up for GitHub

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

Jump to bottom

Update skopeo #6180

Closed
4 of 12 tasks
potyl opened this issue Sep 5, 2022 · 3 comments
Closed
4 of 12 tasks

Update skopeo #6180

potyl opened this issue Sep 5, 2022 · 3 comments
Labels
feature request

Comments

@potyl
Copy link

potyl commented Sep 5, 2022 •
edited
Loading

Tool name

skopeo

Tool license

Apache License Version 2.0

Add or update?

  • Add
  • Update

Desired version

v1.9.2 (latest) or at least v1.5.1 or greater

Approximate size

No response

Brief description of tool

No response

URL for tool's homepage

https://github.com/containers/skopeo

Provide a basic test case to validate the tool's functionality.

skopeo inspect --no-tags docker://docker.io/busybox:latest

Platforms where you need the tool

  • Azure DevOps
  • GitHub Actions

Virtual environments where you need the tool

  • Ubuntu 18.04
  • Ubuntu 20.04
  • Ubuntu 22.04
  • macOS 10.15
  • macOS 11
  • macOS 12
  • Windows Server 2019
  • Windows Server 2022

Can this tool be installed during the build?

I suppose as it is an upgrade to an existing tool.

Tool installation time in runtime

No response

Are you willing to submit a PR?

Yes, if you're so kind to point me to the build instructions
@miketimofeev
Copy link
Contributor

@emo-slido I'm afraid we don't control the upstream repo updates. The new version of skopeo will be delivered right after those repos (https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable for Ubuntu 18&20 and the official Ubuntu repo for Ubuntu22) are updated.
I'm going to close the issue. Please feel free to contact us if you have any concerns.
Thank you!

@al-cheb
Copy link
Contributor

al-cheb commented Sep 5, 2022

As a workaround you can install skopeo in runtime:

- run: |
          sudo apt purge buildah golang-github-containers-common podman skopeo
          sudo apt autoremove --purge
- run: |
          REPO_URL="https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/unstable"
          source /etc/os-release
          sudo sh -c "echo 'deb ${REPO_URL}/x${NAME}_${VERSION_ID}/ /' > /etc/apt/sources.list.d/devel:kubic:libcontainers:unstable.list"
          sudo wget -qnv https://download.opensuse.org/repositories/devel:kubic:libcontainers:stable/x${NAME}_${VERSION_ID}/Release.key -O Release.key
          sudo apt-key add Release.key
          sudo apt-get update
- run: |
          sudo apt-get install skopeo

image

@victorlin
Copy link

According to a blog post, the Kubic Project is now officially wound down. I'm not familiar with it, but it can probably be assumed that this repo won't be updated anymore. Some other possibilities:

  1. Use another well-maintained repo.
  2. Wait for the default source to provide a newer version (e.g. Ubuntu 22 is at skopeo version 1.4.1). Looks like there's some recent activity related to 1.9.2.

victorlin added a commit to nextstrain/docker-base that referenced this issue Oct 22, 2022
@victorlin
copy-images: Use skopeo to "push" images
f7c6031 
Instead of pushing images that are available locally (different from a
local registry) to Docker Hub, the proper way to make them available in
the destination is to copy from the source registry directly without
unnecessary pull/push. This is what skopeo can do.

A containerized version of skopeo is used since the version
pre-installed on the GitHub Actions Ubuntu runners is stuck in the past¹
and does not support --multi-arch², which may be used in the future.

Also note that the tag-latest script is replaced by a conditional block
in the new script which copies the tag from one registry to `latest` on
another another.

¹ actions/runner-images#6180 (comment)
² https://github.com/containers/skopeo/releases/tag/v1.6.0
victorlin added a commit to nextstrain/docker-base that referenced this issue Nov 1, 2022
@victorlin
copy-images: Use skopeo to "push" images
74a4a8c 
Instead of pushing images that are available locally (different from a
local registry) to Docker Hub, the proper way to make them available in
the destination is to copy from the source registry directly without
unnecessary pull/push. This is what skopeo can do.

A containerized version of skopeo is used since the version
pre-installed on the GitHub Actions Ubuntu runners is stuck in the past¹
and does not support --multi-arch², which may be used in the future.

Also note that the tag-latest script is replaced by a conditional block
in the new script which copies the tag from one registry to `latest` on
another another.

¹ actions/runner-images#6180 (comment)
² https://github.com/containers/skopeo/releases/tag/v1.6.0
victorlin added a commit to nextstrain/docker-base that referenced this issue Nov 1, 2022
@victorlin
copy-images: Use skopeo to "push" images
87f1e53 
Instead of pushing images that are available locally (different from a
local registry) to Docker Hub, the proper way to make them available in
the destination is to copy from the source registry directly without
unnecessary pull/push. This is what skopeo can do.

A containerized version of skopeo is used since the version
pre-installed on the GitHub Actions Ubuntu runners is stuck in the past¹
and does not support --multi-arch², which may be used in the future.

Also note that the tag-latest script is replaced by a conditional block
in the new script which copies the tag from one registry to `latest` on
another another.

¹ actions/runner-images#6180 (comment)
² https://github.com/containers/skopeo/releases/tag/v1.6.0
victorlin added a commit to nextstrain/docker-base that referenced this issue Nov 1, 2022
@victorlin
copy-images: Use skopeo to "push" images
ba85eed 
Instead of pushing images that are available locally (different from a
local registry) to Docker Hub, the proper way to make them available in
the destination is to copy from the source registry directly without
unnecessary pull/push. This is what skopeo can do.

A containerized version of skopeo is used since the version
pre-installed on the GitHub Actions Ubuntu runners is stuck in the past¹
and does not support --multi-arch², which may be used in the future.

Also note that the tag-latest script is replaced by a conditional block
in the new script which copies the tag from one registry to `latest` on
another another.

¹ actions/runner-images#6180 (comment)
² https://github.com/containers/skopeo/releases/tag/v1.6.0
victorlin added a commit to nextstrain/docker-base that referenced this issue Dec 15, 2022
@victorlin
copy-images: Use skopeo to "push" images
5b1272c 
Instead of pushing images that are available locally (different from a
local registry) to Docker Hub, the proper way to make them available in
the destination is to copy from the source registry directly without
unnecessary pull/push. This is what skopeo can do.

A containerized version of skopeo is used since the version
pre-installed on the GitHub Actions Ubuntu runners is stuck in the past¹
and does not support --multi-arch², which may be used in the future.

Also note that the tag-latest script is replaced by a conditional block
in the new script which copies the tag from one registry to `latest` on
another another.

¹ actions/runner-images#6180 (comment)
² https://github.com/containers/skopeo/releases/tag/v1.6.0
@natescherer natescherer mentioned this issue Feb 3, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@potyl @victorlin @al-cheb @miketimofeev @mikhailkoliada