[registry-packages] fix containerd-fe build #683
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
modules/007-registrypackages/images/containerd-fe/werf.inc.yaml
Outdated
Show resolved
Hide resolved
RomanenkoDenys
force-pushed
the
fix-containerd-build
branch
from
04b16e7
to
b193838
Compare
konstantin-axenov
approved these changes
Jan 27, 2022
Merged
|
Cherry-picked into release-1.30 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixed build of containerd-fe registry package.
Why do we need it, and what problem does it solve?
After release of registry packages with content tagging, we lost patch in containerd-fe package
Changelog entries