-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker: npm errors (linux) #12970
Comments
Maybe the expedient way to fix this issue and #12971 is to remove the EDIT: This seems to resolve the problem with Linux, but not with Windows (which now emits a different error). |
That doesn't (always) work if the host OS is different from container OS, which is fairly common ... |
I observed something similar on the latest image. Somehow the the home In my case $ podman run -it --rm --entrypoint "sh" ghcr.io/gohugoio/hugo:v0.136.2
/project $ git config --global user.name Test
error: could not lock config file /var/hugo/.gitconfig: Permission denied In this particular case npm is trying to save its cache and failing to create that folder. $ podman run -it --rm --entrypoint "sh" ghcr.io/gohugoio/hugo:v0.136.2
/project $ ls -lld /var/hugo
drwxr-xr-x 3 root root 4096 Oct 17 14:45 /var/hugo $ podman run -it --rm --entrypoint "sh" ghcr.io/gohugoio/hugo:v0.136.1
/project $ ls -lld /var/hugo
drwxr-xr-x 3 hugo nogroup 4096 Oct 20 16:03 /var/hugo From the Dockerfile, my suspicion was the use of chown on two files, but that works fine when I tried similar command on my machine (Fedora Linux). Line 73 in 352be5b
Then I tried to build latest master using podman, resulting image had home directory with correct owner, not sure what's going on 🤷 I don't have access to a Docker installation at the moment, so if someone can try building the image again and see who is owner of |
This is a regression from v0.136.1.
error log
To test:
cc: @dvdksn
The text was updated successfully, but these errors were encountered: