Skip to content

[v1.5] Dockerfile: Bump cilium-runtime to latest image #11626

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

Merged
merged 2 commits into from
May 25, 2020

Conversation

joestringer
Copy link
Member

Update the cilium-runtime image to bump all OS dependencies.

Signed-off-by: Joe Stringer <joe@cilium.io>
@joestringer joestringer requested a review from a team as a code owner May 20, 2020 22:34
@maintainer-s-little-helper maintainer-s-little-helper bot added backport/1.5 kind/backports This PR provides functionality previously merged into master. labels May 20, 2020
@joestringer
Copy link
Member Author

test-me-please

@aanm aanm added the release-note/misc This PR makes changes that have no direct user impact. label May 20, 2020
@joestringer
Copy link
Member Author

never-tell-me-the-odds

1 similar comment
@nebril
Copy link
Member

nebril commented May 21, 2020

never-tell-me-the-odds

@joestringer
Copy link
Member Author

never-tell-me-the-odds

@joestringer joestringer requested a review from a team May 21, 2020 23:51
@joestringer
Copy link
Member Author

Looks like the initial attempt at resolving the certificate issue was ineffective:

https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/19684/execution/node/96/log/

17:53:30      k8s2-1.10: Error response from daemon: Get https://k8s1:5000/v2/: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "cilium.io")

The vagrant box we ship & use with Cilium 1.5 uses certs generated over
one year ago. Given that we intend to sunset Cilium 1.5 soon, rather
than regenerating the certs & box, and dealing with updating the box
image and so on for this branch, instead here we just copy the
registry.sh from the latest cilium/packer-ci-build repository as of
today and call it directly during vagrant provisioning.

Fixes: #11641

Signed-off-by: Joe Stringer <joe@cilium.io>
@nebril nebril force-pushed the pr/v1.5-runtime-bump branch from 117071a to 3dd5376 Compare May 22, 2020 14:33
@nebril
Copy link
Member

nebril commented May 22, 2020

never-tell-me-the-odds

@nebril
Copy link
Member

nebril commented May 22, 2020

Added one last hack:

echo '{"insecure-registries": ["k8s1:5000"]}' > /etc/docker/daemon.json
sudo pkill -SIGHUP docker

this should be enough of a band-aid to keep this from failing.

@maintainer-s-little-helper maintainer-s-little-helper bot added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label May 22, 2020
@tklauser tklauser merged commit b5b0727 into v1.5 May 25, 2020
@tklauser tklauser deleted the pr/v1.5-runtime-bump branch May 25, 2020 07:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/backports This PR provides functionality previously merged into master. ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/misc This PR makes changes that have no direct user impact.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants