TonySpegel / zola-build-action

GitHub Action to build a website with Zola
1 stars 1 forks source link

Error: dubious ownership in repository at '/github/workspace' #1

Open ewpratten opened 1 year ago

ewpratten commented 1 year ago

Hello, I have encountered an issue with this action, just randomly starting today after no changes by myself.

Do you happen to know whats causing this? It appears to be coming from inside the Docker container

Build logs

2023-01-29T19:17:01.7441541Z ##[group]Run TonySpegel/zola-build-action@v1
2023-01-29T19:17:01.7441853Z env:
2023-01-29T19:17:01.7442073Z   CONFIG_FILE: config.toml
2023-01-29T19:17:01.7442306Z ##[endgroup]
2023-01-29T19:17:01.7741971Z ##[command]/usr/bin/docker run --name c62b4a48dd12a41e9a7b3342cd5788fc6_d32551 --label 49859c --workdir /github/workspace --rm -e "CONFIG_FILE" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/ewpratten.com/ewpratten.com":"/github/workspace" 49859c:62b4a48dd12a41e9a7b3342cd5788fc6
2023-01-29T19:17:02.4180517Z Deploying
2023-01-29T19:17:02.4240639Z Fetching themes
2023-01-29T19:17:02.4409085Z fatal: detected dubious ownership in repository at '/github/workspace'
2023-01-29T19:17:02.4410614Z To add an exception for this directory, call:
2023-01-29T19:17:02.4412707Z 
2023-01-29T19:17:02.4413065Z    git config --global --add safe.directory /github/workspace
2023-01-29T19:17:02.5776439Z Post job cleanup.
2023-01-29T19:17:02.7444003Z [command]/usr/bin/git version
2023-01-29T19:17:02.7506197Z git version 2.39.1
ewpratten commented 1 year ago

Here is a permalink to the commit that threw this error on my side: https://github.com/ewpratten/ewpratten.com/tree/56b0ead7b7e652dec40be7d073594616c6cbe6d4

TonySpegel commented 1 year ago

Hi there @ewpratten. I'm glad you somehow stumbled upon my small action - never thought someone would use it. I haven't used it in a while because I planned moving to 11ty ✨someday✨but as far from what I can tell it has to be seomthing from the Docker container itself as the zola tar file is pinned to a specific version and the container image is not. Maybe you could try pinning it to an ealier version?

Actually, and I'm not as sure about it, the reason I created this action was to pass params in a different way as I thought it wasn't possible to do so with the original action. But I think that should be possible.

Could you try pinning the container version for yourself and see if that helps? You could setup your own action and just copy its content from here

ewpratten commented 1 year ago

Ok. I'll try tinkering with it.

Up until now, the action has been working really well. Well enough that I use it in multiple projects (all of these repos except yours were authored by me ;) )

image

TonySpegel commented 1 year ago

I'm really honored, that's so cool. Please keep me updated. I'll try to have a look tomorrow too and see if I can do anything about it. I'm sure we can get that to work again