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

machine-controller-manager-provider-local node image build fails #9

Closed
shafeeqes opened this issue Sep 7, 2022 · 1 comment
Closed
Labels
kind/bug Bug lifecycle/rotten Nobody worked on this for 12 months (final aging stage) status/closed Issue is closed (either delivered or triaged)

Comments

@shafeeqes
Copy link
Contributor

shafeeqes commented Sep 7, 2022

What happened:
machine-controller-manager-provider-local node image build fails with:

#10 [linux/amd64 2/9] RUN apt-get update -yq &&     apt-get install -yq --no-install-recommends wget apparmor apparmor-utils jq
#0 0.193 Ign:1 http://security.ubuntu.com/ubuntu impish-security InRelease
#0 0.210 Err:2 http://security.ubuntu.com/ubuntu impish-security Release
#0 0.210   404  Not Found [IP: 91.189.91.39 80]
#0 0.318 Ign:3 http://archive.ubuntu.com/ubuntu impish InRelease
#0 0.396 Ign:4 http://archive.ubuntu.com/ubuntu impish-updates InRelease
...
#0 0.711 Err:8 http://archive.ubuntu.com/ubuntu impish-backports Release
#0 0.712   404  Not Found [IP: 185.125.190.39 80]
#0 0.719 Reading package lists...
#0 0.725 E: The repository 'http://security.ubuntu.com/ubuntu impish-security Release' does not have a Release file.
#0 0.726 E: The repository 'http://archive.ubuntu.com/ubuntu impish Release' does not have a Release file.
#0 0.728 E: The repository 'http://archive.ubuntu.com/ubuntu impish-updates Release' does not have a Release file.
#0 0.728 E: The repository 'http://archive.ubuntu.com/ubuntu impish-backports Release' does not have a Release file.
#10 ERROR: process "/bin/sh -c apt-get update -yq &&     apt-get install -yq --no-install-recommends wget apparmor apparmor-utils jq" did not complete successfully: exit code: 100
------

Ref
This is due to kubernetes-sigs/kind#2863, and it is fixed in the kindest/node:v1.25.0 image but we cannot use this yet because of gardener/gardener#5325

What you expected to happen:
Node image build to be successful.

How to reproduce it (as minimally and precisely as possible):
Run docker build -t test:v1 ./node/. locally with the current kind image (

).
and see it fail on step:
RUN apt-get update -yq && \
apt-get install -yq --no-install-recommends wget apparmor apparmor-utils jq

with the above error.

Run again with kindest/node:v1.25.0 and see it passes.
Anything else we need to know:

Environment:

@shafeeqes shafeeqes added the kind/bug Bug label Sep 7, 2022
@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label May 17, 2023
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jan 24, 2024
@oliver-goetz
Copy link
Member

This is fixed meanwhile.

@gardener-robot gardener-robot added the status/closed Issue is closed (either delivered or triaged) label Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Bug lifecycle/rotten Nobody worked on this for 12 months (final aging stage) status/closed Issue is closed (either delivered or triaged)
Projects
None yet
Development

No branches or pull requests

3 participants