Replies: 2 comments 6 replies
-
Earlier I stated that it wasn't needed yet since the environment requirements are trivial, but I've since changed my mind about that due to popular demand for a Dockerfile to be included in the repo. This is one I wrote earlier and shared on Discord: FROM node:21-alpine
RUN apk add --no-cache bash # useful for debugging
RUN mkdir -p /opt/puter/app
WORKDIR /opt/puter/app
COPY . .
RUN chown -R node:node /opt/puter/app
USER node
RUN npm install
EXPOSE 4000
CMD [ "npm", "start" ] In your Dockerfile, what's the rationale for cloning the repo as a step in the build? I think it would make it inconvenient for people to build docker images for forks or with local changes. |
Beta Was this translation helpful? Give feedback.
-
@vluz somebody PR'd a very simple Dockerfile that I just merged, but I'm going to go through your Dockerfile shortly and add the labels and cache clearing you contributed. I've also added this poll to continue this discussion and make a decision with the community. I actually think this is really interesting. |
Beta Was this translation helpful? Give feedback.
-
Hello!
I'd like to contribute a Dockerfile to the project.
Tested under Docker and Podman.
Happy to modify for any purpose and answer questions.
Beta Was this translation helpful? Give feedback.
All reactions