Validation Required for Runtime Package Installation on uhg-runner
Open
Nobody has claimed this yet.
bug
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
Hi Team,
Our Database Deployment GitHub Actions workflow running on uhg-runner requires the following MySQL runtime dependencies:
- libncurses6
- libtinfo6
- libaio1
Currently, these dependencies are being installed during workflow execution using sudo apt-get because the MySQL client fails with the following error:
mysql: error while loading shared libraries: libncurses.so.6: cannot open shared object file: No such file or directory
Could you please confirm the following:
- Is sudo apt-get usage permitted on uhg-runner?
- Is uhg-runner an ephemeral runner or a persistent shared runner?
- If runtime package installation is not recommended, can these dependencies be pre-installed on the runner image?
- Since GitHub Actions container jobs are supported, is there an approved base container image available that already contains:
- MySQL Client
- jq
- libncurses
- libtinfo
- libaio
- What is the recommended enterprise-supported approach for handling these dependencies on uhg-runner?
Current workflow dependencies:
- MySQL Client -latest
- jq 1.7.1
- libncurses6
- libtinfo6
- libaio1
Please advise on the preferred approach so that we can align the implementation with platform and security standards.
Thanks.
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 by reviewing the Database Deployment GitHub Actions workflow and the uhg-runner/container-job guidance; the issue names no repository file or test. Determine the supported package-installation policy, runner lifecycle, and approved image or dependency approach, then document a maintainer-confirmed recommendation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, mysql
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100