permission issue on windows

[rayenhidri27]

i'm following your video on youtube and i arrived to 39 min i had an error
first, when i type this command

docker run -p 5173:5173 -v "$(pwd):/app" -v /app/node_modules react-docker

it don't work => i searched on internet, and it's told that i should type the absolute path to the folder, so i typed :

docker run -p 5173:5173 -v "C:/Users/asus/Desktop/docker_course/react-docker:/app" -v /app/node_modules react-docker

but i had an error as you can see in he screenshot below

[rayenhidri27]

for information, i tried to use other consoles like git, power shell
even as admin in the default terminal and power shell as a try to have rights, but no changes

[meyoh-23]

after all the docker commands, you should specify the script you want to run eg, if you created your react app with vite, you can and the script run dev. I worked for me. I did paste the error message to chatGPT and their suggestions worked for me. You can try that too.

…

On Sun, Jan 21, 2024 at 8:37 AM rayen hidri ***@***.***> wrote: for information, i tried to use other consoles like git, power shell even as admin in the default terminal and power shell as a try to have rights, but no changes — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZOKVTYGFDGH5KO2UPS6AMLYPSSRRAVCNFSM6AAAAABCDWYPK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBSGUYTSMJWGQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[itpaulin]

I'm having the same problem, I use WSL2 and I fix this part with --user root in the end of cli, but with 'sudo docker compose up' I didn't find any solution yet

[rayenhidri27]

after all the docker commands, you should specify the script you want to run eg, if you created your react app with vite, you can and the script run dev. I worked for me. I did paste the error message to chatGPT and their suggestions worked for me. You can try that too.
…
On Sun, Jan 21, 2024 at 8:37 AM rayen hidri @.> wrote: for information, i tried to use other consoles like git, power shell even as admin in the default terminal and power shell as a try to have rights, but no changes — Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZOKVTYGFDGH5KO2UPS6AMLYPSSRRAVCNFSM6AAAAABCDWYPK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBSGUYTSMJWGQ . You are receiving this because you are subscribed to this thread.Message ID: @.>

i'm sorry i don't understand what do you mean
can you give more details please ?

[karkiahmedraid]

The solution is easy just make a change in your Dockerfile and delete this line USER app at line 34

set the base image to create the image for react app

FROM node:21-alpine3.18

create a user with permissions to run the app

-S -> create a system user

-G -> add the user to a group

This is done to avoid running the app as root

If the app is run as root, any vulnerability in the app can be exploited to gain access to the host system

It's a good practice to run the app as a non-root user

RUN addgroup app && adduser -S -G app app

set the user to run the app

USER app

set the working directory to /app

WORKDIR /app

copy package.json and package-lock.json to the working directory

This is done before copying the rest of the files to take advantage of Docker’s cache

If the package.json and package-lock.json files haven’t changed, Docker will use the cached dependencies

COPY package*.json ./

sometimes the ownership of the files in the working directory is changed to root

and thus the app can't access the files and throws an error -> EACCES: permission denied

to avoid this, change the ownership of the files to the root user

USER root

change the ownership of the /app directory to the app user

chown -R :

chown command changes the user and/or group ownership of for given file.

RUN chown -R app:app .

change the user back to the app user

this one => #USER app

install dependencies

RUN npm install

copy the rest of the files to the working directory

COPY . .

expose port 5173 to tell Docker that the container listens on the specified network ports at runtime

EXPOSE 5173

command to run the app

CMD npm run dev

[shourov00]

For windows keep the docker run as it is.

docker run -p 5173:5173 -v "$(pwd):/app" -v /app/node_modules react-docker

Make sure to change the vite.config.ts file

import {defineConfig} from 'vite'
import react from '@vitejs/plugin-react'

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react()],
  server: {
    watch: {
      usePolling: true, // This is needed to reflect the code changes with docker
    },
  }
})

[thanhliemtu]

For windows keep the docker run as it is.

docker run -p 5173:5173 -v "$(pwd):/app" -v /app/node_modules react-docker

Make sure to change the vite.config.ts file

import {defineConfig} from 'vite'
import react from '@vitejs/plugin-react'

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react()],
  server: {
    watch: {
      usePolling: true, // This is needed to reflect the code changes with docker
    },
  }
})

Still getting " EACCES: permission denied" despite changing vite.config.ts file

[et69]

I had the same issue on my Ubuntu Desktop and I found the solution. It is because the directory in the container become owned by root in bind mount and it is the default behavior of "Docker Desktop" . I have both Docker Engine and Docker Desktop installed on my machine and when I tested with Docker Engine (not Docker Desktop), the directory in the container has the same ownership as the directory in the host.