👀 Views: 426 💬 Answers: 1 📅 Created: 2025-08-24

docker ubuntu node.js Dockerfile

I'm reviewing some code and I tried several approaches but none seem to work..... I'm struggling to start a Docker container on my Ubuntu 22.04 LTS machine. I built my Docker image from a Dockerfile that pulls from the official Node.js image. However, when I try to run the container, I get the following behavior message: ``` standard_init_linux.go:228: exec user process caused "no such file or directory" ``` I've verified that the entry point in my Dockerfile is set correctly: ```dockerfile FROM node:16 WORKDIR /app COPY . . RUN npm install CMD ["node", "server.js"] ``` The `server.js` file is definitely in the root of the copied files. I've checked the line endings of `server.js` and ensured they're set to Unix (LF) instead of Windows (CRLF), as I suspect that might be causing the scenario. I even tried rebuilding the image using `docker build --no-cache -t myapp .` to ensure there were no caching issues. Additionally, I executed `docker run --rm -it myapp /bin/bash` to enter the container and confirmed that `node` exists in the path by running `which node`, which returned `/usr/local/bin/node`. Despite this, the container fails to start correctly. I would appreciate any insights into what could be causing this scenario. Could it be related to the way Docker interprets the entry point or how the files were copied? Any help would be greatly appreciated! For context: I'm using Dockerfile on Ubuntu. For reference, this is a production REST API. I'm developing on macOS with Dockerfile. Is this even possible?