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

Add libc6 to Dockerfile in run stage #5323

Closed
wants to merge 1 commit into from

Conversation

AliKarami
Copy link

we found that in v5.21.0 there is missing GLIBC_2.28 requirement and pod crashes. so we add libc6 package which solves the issue.

Issue

fix crashes caused by missing GLIBC_2.28 requirement.

Tasklist

Requirements / Relations

we found that in v5.21.0 there is missing `GLIBC_2.28` requirement and pod crashes. so we add `libc6` package which solves the issue.
@amirmasud
Copy link

amirmasud commented Dec 19, 2018

The problem seems to be caused by gcc package dependencies where it uses libc6-dev as mentioned here and on run-stage the previous Dockerfile didn't add libc6 and the libc6 version wasn't the same. so by adding the package as @AliKarami did, the problem should be solved.

@danpat
Copy link
Member

danpat commented Dec 19, 2018

Ugh. I missed that the Dockerfile depends on buster, which is still testing - dependencies may still change over time. It might be preferable to switch to stretch which is considered stable.

We should also add some tests for this dockerfile to catch this stuff....I'll look into that.

Copy link

@amirmasud amirmasud left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the libc6 is a dependency of libc6-dev which also is a dependency of gcc we can be sure that it won't cause any further issues in the future :)

@danpat
Copy link
Member

danpat commented Jan 12, 2019

I decided to avoid the currently unstable state of buster and go with the downgrade to stretch-slim over in #5338

@danpat danpat closed this Jan 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants