Skip to content
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 image permission issue when run in GitHub Action #12991

Open
theory opened this issue Oct 28, 2024 · 14 comments
Open

Docker image permission issue when run in GitHub Action #12991

theory opened this issue Oct 28, 2024 · 14 comments

Comments

@theory
Copy link
Contributor

theory commented Oct 28, 2024

What version of Hugo are you using (hugo version)?

❯ docker run ghcr.io/gohugoio/hugo:v0.136.5 version                      
hugo v0.136.5+extended linux/arm64 BuildDate=unknown VendorInfo=docker

Does this issue reproduce with the latest release?

Yes.

It looks like b5852d0 fixed #12946, but now, using v0.136.5, I get a new error:

Error: error building site: failed to acquire a build lock: open /github/workspace/.hugo_build.lock: permission denied

I suspect this is because the Docker image runs as hugo:hugo by default, but GitHub, for better or worse, requires that processes in Docker run as root in order to have permission to write files and whatnot.

@jmooring
Copy link
Member

cc: @dvdksn

@dvdksn
Copy link
Contributor

dvdksn commented Oct 28, 2024

You can probably just add the lock file to dockerignore and it'll work.

Can you share your workflow and Dockerfile please.

@theory
Copy link
Contributor Author

theory commented Oct 28, 2024

Here's my workflow, and here is the project Dockerfile.

@bep bep removed the NeedsTriage label Oct 29, 2024
@bep bep changed the title Docker image needs ability to run as root to work as a GitHub Action Docker image permission issue when run in GitHub Action Oct 29, 2024
@bep bep added this to the v0.137.0 milestone Oct 29, 2024
@bep
Copy link
Member

bep commented Oct 29, 2024

Error: error building site: failed to acquire a build lock: open /github/workspace/.hugo_build.lock: permission denied

Possible workaround:

hugo  --noBuildLock  

@dvdksn
Copy link
Contributor

dvdksn commented Oct 29, 2024

@bep how do you feel about letting this image run as root? There have already been quite a few issues related to permissions. Users wouldn't typically run this image in production, but as a build step, so I don't really think running as root would be a security concern.

@jmooring
Copy link
Member

Users wouldn't typically run this image in production

Why not?

It seems like we began this effort (many hours now) without a clear definition of intended use:

  • Local builds?
  • CI/CD container?
  • CI/CD build step?

I created an image several months ago as a learning/testing exercise, and use it with both GitHub Pages and GitLab Pages as demonstrated with this test site:

It can also be used for local builds.

I'm not advocating that we use this test image, but its composition intentionally targeted the use cases above.

Other than documentation and support I don't have a stake in this. But it would be good if the target stopped moving.

@bep
Copy link
Member

bep commented Oct 29, 2024

I'm not advocating that we use this test image, but its composition intentionally targeted the use cases above.

I don't see any Docker file referenced, so it's hard to say anything about this particular image, but a quick glance at your CI setup, I'm guessing it's setup differently (without e.g. Node/NPM).

Users wouldn't typically run this image in production

  1. Building a Hugo site for production is the primary use case for this, and both CI container and CI build step (assuming there's a difference) should work (assuming the platform OS/arch is supported).
  2. Local development should work, but that sounds like a secondary use case to me.
  3. Hugo's server is a development server, so running hugo server in production is not something we will support/encourage.

@theory
Copy link
Contributor Author

theory commented Oct 29, 2024

Using --noBuildLock just gets the build to the next permission issue:

Error: error copying static files: mkdir /github/workspace/public: permission denied

I created an image several months ago as a learning/testing exercise, and use it with both GitHub Pages and GitLab Pages as demonstrated with this test site:

From the Dockerfile, it looks like you never set the user, so it will run as root, which is what GitHub actions, at least, require.

@theory
Copy link
Contributor Author

theory commented Oct 29, 2024

  1. Building a Hugo site for production is the primary use case for this, and both CI container and CI build step (assuming there's a difference) should work (assuming the platform OS/arch is supported).

If you mean it builds the static files and they get deployed somewhere, but the image itself isn't spun up to serve the site or do anything else for a production server, then it seems as though it doesn't matter whether it runs as root or not.

@bep bep self-assigned this Oct 29, 2024
@dvdksn
Copy link
Contributor

dvdksn commented Oct 29, 2024

If you mean it builds the static files and they get deployed somewhere, but the image itself isn't spun up to serve the site or do anything else for a production server, then it seems as though it doesn't matter whether it runs as root or not.

This is what I meant. We only care about static output generated from the container. So the user privileges in the container are only relevant at build-time (and/or during development), which is why I think running as root is probably fine for this image.

@theory
Copy link
Contributor Author

theory commented Oct 29, 2024

This is what I meant. We only care about static output generated from the container. So the user privileges in the container are only relevant at build-time (and/or during development), which is why I think running as root is probably fine for this image.

I think so, too.

@bep bep modified the milestones: v0.137.0, v0.138.0 Oct 30, 2024
@bep bep removed their assignment Oct 30, 2024
@bep
Copy link
Member

bep commented Oct 30, 2024

OK, I have spent some time on this today, and my conclusions are:

  • This works if we remove the USER setups in the Dockerfile, e.g. run as root.
  • I wouldn't mind running as root in GitHub Actions.
  • I would not like if docker run ... server ran as root when started on my development PC.

And when I say I above, I'm also assuming a lot of other Hugo users' having the same view on things.

I don't have a practical solution for this, I'm afraid; I suspect the solution might be to set up a separate "Hugo GitHub Action".

@theory
Copy link
Contributor Author

theory commented Oct 30, 2024

Well, GitHub actions don't run the ENTRYPOINT, so you can use gosu in the entry point script to create and execute as a less privileged user. Here's an example.

@bep bep modified the milestones: v0.137.0, v0.138.0 Oct 31, 2024
@phante
Copy link

phante commented Nov 4, 2024

Hi,
I think this kind of problem can be generalized for all CI/CD systems that are based on containerized images.

I also encountered it using Woodpecker CI because in that case the git repository pull step is done with root user and therefore the Hugo image is not able to write inside the directory tree.

On my pipeline I solved it by adding between the workspace download and the hugo execution a step that changes the owner of the file inside the workspace to hugo (uid 1000).

@bep bep modified the milestones: v0.138.0, v0.139.0 Nov 6, 2024
@bep bep modified the milestones: v0.139.0, v0.140.0 Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants