QuestionAccepted answer
error "/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found"
Jahadul Rakib
09 Aug 2026, 16:02 UTC
95.2K views1
Here is My Dockerfile:
FROM ubuntu:20.04
RUN apt-get update && apt-get upgrade -y
RUN apt-get install libssl-dev
RUN apt-get install -y -q build-essential curl
RUN curl https://sh.rustup.rs -sSf | sh -s -- -y
ENV PATH="/root/.cargo/bin:${PATH}"
WORKDIR /command-agent
COPY . /command-agent
RUN cargo build --release
COPY /command-agent/target/release/command-agent /
EXPOSE 8080
ENTRYPOINT command-agent
Its build successfully docker image but when I run that container its gives error:
command-agent: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /command-agent/command-agent)
I do not understand, How can I fix this issue ?
rust
ubuntu
linux1 answer
Accepted answer · original discussion
Jahadul Rakib
Permalink14 Aug 2026, 11:14 UTC
ITs works for me when i avoid /target directory and now working both version of ubuntu 20.04 and 21.10. Giving thanks to @Charles Duffy and @Herohtar for their important and useful instruction,
FROM ubuntu:21.10
RUN apt-get update && apt-get upgrade -y
RUN apt-get install libssl-dev
RUN apt-get install -y -q build-essential curl
RUN curl https://sh.rustup.rs -sSf | sh -s -- -y
ENV PATH="/root/.cargo/bin:${PATH}"
WORKDIR /command-agent
COPY ./src/. /command-agent/src/
COPY .env /command-agent/
COPY Cargo.toml /command-agent/
COPY Cargo.lock /command-agent/
RUN cargo build --release
EXPOSE 8080
ENTRYPOINT /command-agent/target/release/command-agent
3 question comments
Use comments to ask for clarification. Post a solution as an answer.
Charles DuffyPermalink
10 Aug 2026, 20:50 UTC
Means exactly what it says -- you're not running against the same libc that compilation was against. Be sure you compile executables on the same platform you're going to run them on unless you're going to make sure they're static.
HerohtarPermalink
12 Aug 2026, 01:38 UTC
@CharlesDuffy has a good point. Unless you have a
.dockerignore file set up correctly, the target directory will also be copied, and then the cargo build command will not actually rebuild if you have already run the build locally.