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

libatomic.so.1: cannot open shared object file: No such file or directory while building ingress nginx v1.11.2 #12404

Open
ajsmksja opened this issue Nov 25, 2024 · 2 comments
Labels
kind/support Categorizes issue or PR as a support question. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@ajsmksja
Copy link

What happened:

While building the Ingress controller v1.11.2, facing the below error related to libatomic v1.11.2,
libatomic.so.1: cannot open shared object file: No such file or directory

What you expected to happen:
as a Work Around, added the libatomic in the base image/nginx dockerfile, so that the build is successful

would like to know, if this WA is good to proceed with or any suggested way of handling this issue.

NGINX Ingress controller version
NGINX Ingress controller
Release: 1.11.2
Build: git-be46124cc
Repository: https://github.com/kubernetes/ingress-nginx.git
nginx version: nginx/1.25.5

Kubernetes version
Client Version: v1.31.2
Kustomize Version: v5.4.2
Server Version: v1.29.1

@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority labels Nov 25, 2024
@strongjz
Copy link
Member

/triage needs-information
/kind support

How did you try to build the image? Was the controller image? Or the base nginx image? Both?

Please add your steps to reproduce the issue.

We've had issues with GCP cloud build lately due to kernel issues, which might affect it as well.

@k8s-ci-robot k8s-ci-robot added triage/needs-information Indicates an issue needs more information in order to work on it. kind/support Categorizes issue or PR as a support question. and removed needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
Development

No branches or pull requests

3 participants