dotnet / dotnet/sdk-container-builds
Configurably emit OCI or Docker manifests
Open
Area: Library
Area: Registries
- Dominant language
- No language data
- Stars
- 197
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Currently most `MediaType` type things are hardcoded to Docker types, but we should be OCI compliant as well (configurably).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by searching the repository for MediaType handling and the Docker-specific manifest values mentioned in the issue. Trace where those values are selected during image creation, then identify the existing configuration entry points and tests around manifest generation. Done means the tooling can select either Docker or OCI manifests through a documented configuration path, with coverage for both choices.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100