Replies: 1 comment
-
Atm, I've built my own Dockerfile from scratch. It seems to work properly. FROM ubuntu:24.04
ENV SHELL /bin/bash
RUN apt-get update && \
apt-get install -y \
make \
git \
openssl \
curl \
unzip
RUN curl -fsSL https://deb.nodesource.com/setup_20.x | bash -
RUN apt-get install -y nodejs
ENV PNPM_HOME="/root/.local/share/pnpm"
ENV PATH="$PNPM_HOME:$PATH"
RUN npm install -g pnpm && \
pnpm setup && \
pnpm i -g pnpm
RUN curl -fsSL https://bun.sh/install | bash -s "bun-v1.1.13"
WORKDIR /app
COPY . .
ENV PATH="/root/.bun/bin:${PATH}"
EXPOSE 3000
CMD ["make", "docker-app-entrypoint"] |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Seems to be related to: #4848 / prisma/prisma#21241
Hello!
I have an issue, using Bun 1.1.13, Docker version 26.1.4, and Docker Compose version v2.27.1.
When I run
docker compose up -d
and then inspect the logs of my container, I see this message:This is weird, I don't understand why it happens?
Here's my Dockerfile:
I thought that installing the latest version of OpenSSL with apt-get would be enough.
It seems to not be the case.
I would like to know if there is any specific reasons behind this?
Does the Bun Docker image intended to use a older version of OpenSSL, and would it exposes me to some vulns?
I feel uncomfortable with the "straightforward" way to hide the problem, appending
binaryTargets = ["debian-openssl-1.1.x"]
within my Prisma Schema file.As I'm not sure yet whether the problem is more on the Prisma side or more on the Bun side, I'm asking here for now (in the discussions section).
Note that before I started docking my app, everything worked absolutely perfectly on my Ubuntu machine. With OpenSSL 3.0.2. I'm sure it could work just as well in a Docker container.
(I'm also a Docker newbie, sorry!)
Beta Was this translation helpful? Give feedback.
All reactions