Running docker currently mounts the docker.sock file into the container.
This was introduced in d6c937fe37 but
there is no explanation provided.
The docker.sock file is only needed if we want to run docker inside the container
to create other images or start other containers.
I searched through the code and I did not find any such use.
In particular, on fedora this gives permission denied because docker.sock
is owned by root and the container runs under an unprivileged user.
One has to change the permissions of docker.sock
(which is actually a link to /run/podman/podman.sock) to be writeable by the user.
If we don't need to use docker inside the containers, then we can remove this file,
thus we can run this GitHub action as an unprivileged user out of the box.
* feat: support self-hosted runners
similar to https://github.com/game-ci/unity-builder/pull/355
* Use $RUNNER_TEMP variable instead of hardcoded path for _github_home and _github_workflow
* create the folders if they don't exist
* mount volumes with :z for compatibility with SELinux
* compile typescript files
* Refactor to typescript
* Fix platform and workflow
* Fix workflow and platform
* Update husky and image-tag
* Use 'yarn lint-staged' instead of 'npx lint-staged'
Aaron Trudeau
Nick Maltbie
Webber Takken
Paul Pacheco
David Finol