-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[release-v3.27] Sync Calico node arm64 Dockerfile with amd64 #8533
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
This change syncs Calico node arm64 Dockerfile with amd64. It also removes an `ARCH` environment variable definition as it conflicts with the same variable defined in other Makefiles. Calico node Dockerfiles are architecture dependent so arch info are hard-coded now until we unify them.
marvin-tigera
added
release-note-required
Change has user-facing impact (no matter how small)
docs-pr-required
Change is not yet documented
labels
Feb 19, 2024
hjiawei
force-pushed
the
node-dockerfile-sync-327
branch
from
February 19, 2024 22:25
687be26
to
cd811e1
Compare
hjiawei
commented
Feb 20, 2024
node/Dockerfile.arm64
Outdated
Comment on lines
240
to
242
# Node is build on a debian image with pcap 1.8, but there is no 1.8 available so we copy 1.9 over. Ideally we should | ||
# should build node on a centos image so we can have correct pcap version alignment. | ||
RUN ln -s $(ls /usr/lib64/libpcap.so.1.9.* | tail -n 1) /usr/lib64/libpcap.so.0.8 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change should fix #8407 for v3.27 arm64. They are not needed in the main branch as we reworked our toolchain.
coutinhop
reviewed
Feb 20, 2024
coutinhop
approved these changes
Feb 20, 2024
1 task
ScheererJ
added a commit
to gardener/gardener
that referenced
this pull request
Apr 2, 2024
gardener-prow bot
pushed a commit
to gardener/gardener
that referenced
this pull request
Apr 2, 2024
* Update dependency projectcalico/calico to v3.27.3 * Remove comment as projectcalico/calico#8533 resolved the issue for v3.27.3 --------- Co-authored-by: Johannes Scheerer <johannes.scheerer@sap.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
docs-pr-required
Change is not yet documented
release-note-required
Change has user-facing impact (no matter how small)
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
This change syncs Calico node arm64 Dockerfile with amd64. It also removes an
ARCH
environment variable definition as it conflicts with the same variable defined in other Makefiles. Calico node Dockerfiles are architecture dependent so arch info are hard-coded now until we unify them.Related issues/PRs
Pick #8532 into release-v3.27 release branch.
Fixes #8407 for arm64.
Todos
Release Note
Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one
docs-*
label.docs-pr-required
: This change requires a change to the documentation that has not been completed yet.docs-completed
: This change has all necessary documentation completed.docs-not-required
: This change has no user-facing impact and requires no docs.Every PR needs one
release-note-*
label.release-note-required
: This PR has user-facing changes. Most PRs should have this label.release-note-not-required
: This PR has no user-facing changes.Other optional labels:
cherry-pick-candidate
: This PR should be cherry-picked to an earlier release. For bug fixes only.needs-operator-pr
: This PR is related to install and requires a corresponding change to the operator.