Fixed Permission Denied error when running on Docker #31
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ChubaOraka
force-pushed
the
fix-docker-permission-denied-error
branch
from
547cd64
to
d96f6a0
Compare
…tainer's default non-root user `node`
Error Log:
client | [Error: EACCES: permission denied, open '/usr/src/app/client/.next/package.json'] {
client | errno: -13,
client | code: 'EACCES',
client | syscall: 'open',
client | path: '/usr/src/app/client/.next/package.json'
client | }
References:
node.js - How to keep node_modules inside container while using docker-compose and a non-root user? - Stack Overflow
https://stackoverflow.com/questions/49941708/how-to-keep-node-modules-inside-container-while-using-docker-compose-and-a-non-r
https://stackoverflow.com/a/49952703
https://stackoverflow.com/questions/49941708/how-to-keep-node-modules-inside-container-while-using-docker-compose-and-a-non-r/49952703#49952703
Docker Compose mounts named volumes as 'root' exclusively · Issue #3270 · docker/compose · GitHub
docker/compose#3270
Stuck with a Problem of access permission denied · Issue #8908 · vercel/next.js · GitHub
vercel/next.js#8908
vercel/next.js#8908 (comment)
What is the best way to use NextJS with docker? · Discussion #16995 · vercel/next.js · GitHub
vercel/next.js#16995
reactjs - error An unexpected error occurred: "EACCES: permission denied - Stack Overflow
https://stackoverflow.com/questions/52713928/error-an-unexpected-error-occurred-eacces-permission-denied
docker - Dockerfile with nextjs and puppteer permission denied - Stack Overflow
https://stackoverflow.com/questions/64565062/dockerfile-with-nextjs-and-puppteer-permission-denied
[RUN chown -Rh $user:$user /home/node]
https://stackoverflow.com/a/64922590
https://stackoverflow.com/questions/64565062/dockerfile-with-nextjs-and-puppteer-permission-denied/64922590#64922590
[More relevant for production build, suggests we modify next.config.js by adding a distDir directive:
module.exports = {
distDir: 'build',
serverRuntimeConfig: {
// Will only be available on the server side
apiUrl: 'http://signup-api:1984'
},
publicRuntimeConfig: {
// Will be available on both server and client
apiUrl: 'http://localhost:1984'
}
}
]
ChubaOraka
force-pushed
the
fix-docker-permission-denied-error
branch
from
d96f6a0
to
e9e8216
Compare
simplytunde
approved these changes
Aug 23, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #30
Turns out the volume mounts are done as root. I
chowned the.nextandnode_modulesfolders and this fixes the problem.