How to use `termux-docker` in GitHub Actions?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 731
- Forks
- 109
- PR merge metrics
- No merged PRs in 30d
Description
Hello, I want to test a bash installer script within the termux-docker image using GitHub Actions. While GitHub Actions does support running commands within a custom docker image/container, it does not honor the ENTRYPOINT of the image and insists on running everything as root. Even running the commands explicitly under /entrypoint.sh ... to drop privileges does not seem to work properly, due to permission issues. It also seems that the GitHub Actions actions/checkout module expects node to be installed at /__e/node20/bin/node. I also encountered strange networking issues when executing /entrypoint.sh ... multiple times. Is termux-docker even compatible with GitHub Actions? Maybe this is something that could be documented better?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .github/workflows/ronin-install.yml, the referenced termux-docker image behavior, and /entrypoint.sh. Reproduce the GitHub Actions run, including actions/checkout, root execution, repeated entrypoint calls, and networking. Done means establishing whether the image is compatible and documenting the required configuration or its limitations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, shell
- Domain
- ci-cd, devops
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100