concourse / concourse/docker-image-resource
Cannot change default Docker STARTUP_TIMEOUT
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 162
- Forks
- 250
- PR merge metrics
- No merged PRs in 30d
Description
We are running into
very often.
I tried to overcome this by adding a STARTUP_TIMEOUT to the put steps params, but it seems to have no effect.
- put: artifactory-docker-image
params:
load_tag: ((.:version-from-file))
load_file: master-branch/build/image.tar
load_repository: ((artifact_image_path))/((artifact_id))
tag_file: version/version
tag_as_latest: true
STARTUP_TIMEOUT: 180
get_params:
skip_download: true
If the setting being ignored is not a bug, how can this timeout be configured?
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 with the Docker resource's put step and the YAML params block shown in the issue, especially STARTUP_TIMEOUT and the image.tar load path. Trace how the put step reads startup settings and verify whether the supplied timeout reaches the Docker startup operation. Done means the documented setting is honored or the supported configuration path is clearly identified, with a regression test if the project has one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100