OpenDroneMap / OpenDroneMap/ODM
Alpine Linux base image
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 1.3k
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 4
Description
We have someone willing and able to test migrating the base images for WebODM to Alpine Linux, thus enforcing musl lbc, no systemd userland thus elimitating most CVEs, etc. etc.. Before diving into the project wanted to check interest on the WebODM side and if there's interest, logistics to look out for from go.
We'd start with lower complexity images, e.g. redis. And if all images were migrated, we'd have to address the ODM base image as well. But, best to start downstream of ODM and where most of the images are built.
Contributor guide
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 how the Redis and other downstream images are built, then assess the migration path to Alpine Linux and its musl-based userland. The issue names no files or tests; begin with the lower-complexity images and define completion across those images before addressing the ODM base image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, linux
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100