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

Missing containerd.io package in cache #95

Closed
3 tasks done
cevich opened this issue Oct 1, 2021 · 1 comment · Fixed by containers/buildah#3562 or containers/podman#11834
Closed
3 tasks done

Missing containerd.io package in cache #95

cevich opened this issue Oct 1, 2021 · 1 comment · Fixed by containers/buildah#3562 or containers/podman#11834
Assignees

Comments

@cevich
Copy link
Member

cevich commented Oct 1, 2021

Ref: Temporary fix - https://github.com/containers/podman/pull/11821/files#diff-f3866c83e5fdf3650df2ad5b9c0c18efaa71891d23675732cc931e90fd2b10faR261

  • Check if package is actually cached
  • Check if buildah CI has this problem
  • Consider removing --ignore-missing from podman & buildah CI.
@cevich
Copy link
Member Author

cevich commented Oct 1, 2021

Hypothesis: At the end of building VM images, the scripts wipe all the packaging metadata to help reduce image size. So at runtime, this necessitates a apt-get -qq -y update, but (obviously) this is happening later and so may grab newer package info. The result is, a subsequent apt-get install --yes --no-download --ignore-missing just skips the cached package, as it's not represented in the newer metadata.

cevich added a commit to cevich/buildah that referenced this issue Oct 1, 2021
During VM image build, a number of packages are downloaded but not
installed, since they may interfere with some testing.  Then at runtime,
where required, the packages are installed from cache and used.  This
mechanism broke, and is being investigated in
containers/automation_images#95

Signed-off-by: Chris Evich <[email protected]>
cevich added a commit to cevich/buildah that referenced this issue Oct 1, 2021
During VM image build, a number of packages are downloaded but not
installed, since they may interfere with some testing.  Then at runtime,
where required, the packages are installed from cache and used.
However, between image build and runtime it's possible the repository
contents change, which will invalidate the package cache.  Since the
`--no-download --ignore-missing` options were used, the install will
fail.

Ref: containers/automation_images#95

Fortunately, when it comes to the docker packages, no other dependencies
are required and so `apt-get` isn't required.  Switch to using a simple
dpkg install command on the necessary files.  If this ever breaks due
to new dependencies, the list of files may simply be updated.

Signed-off-by: Chris Evich <[email protected]>
cevich added a commit to cevich/podman that referenced this issue Oct 1, 2021
Original workaround containers#11821

During VM image build, a number of packages are downloaded but not
installed, since they may interfere with some testing.  Then at runtime,
where required, the packages are installed from cache and used.
However, between image build and runtime it's possible the repository
contents change, which will invalidate the package cache.  Since the
`--no-download --ignore-missing` options were used, the install will
fail.

Ref: containers/automation_images#95

Fortunately, when it comes to the docker packages, no other dependencies
are required and so `apt-get` isn't required.  Switch to using a simple
dpkg install command on the necessary files.  If this ever breaks due
to new dependencies, the list of files may simply be updated.

Signed-off-by: Chris Evich <[email protected]>
@cevich cevich closed this as completed Feb 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant