envbuilder: use container entrypoint if ENVBUILDER_INIT_SCRIPT is not set
Open
- Dominant language
- Go
- Stars
- 300
- Forks
- 64
- Avg merge
- 20m
- Merged PRs (30d)
- 1
Description
By default, envbuilder runs `/bin/sh -c sleep infinity` as the entrypoint.
This behaviour can be surprising, so we should default to the entrypoint defined in the container if `ENVBUILDER_INIT_SCRIPT` / `ENVBUILDER_INIT_COMMAND` are not set.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the handling of ENVBUILDER_INIT_SCRIPT and ENVBUILDER_INIT_COMMAND, then trace where the default `/bin/sh -c sleep infinity` entrypoint is selected. Verify that the container-defined entrypoint is used when both variables are unset, while the existing environment-variable overrides still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100