Skip to content

Commit

Permalink
Add --force to docker commands (#4820)
Browse files Browse the repository at this point in the history
## Description of the changes
- `docker prune` commands will, by default, prompt the caller whether if
they want to proceed, while defaulting to `N`, which resulted in a no-op
in this [recent CI
run](https://github.com/jaegertracing/jaeger/actions/runs/6442084773/job/17492537692#step:19:735).
- Adding a `--force` flag defaults to `y` without a prompt.

## How was this change tested?
- Tested locally in terminal.

## Checklist
- [x] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [x] I have signed all commits

Signed-off-by: albertteoh <see.kwang.teoh@gmail.com>
  • Loading branch information
albertteoh authored Oct 7, 2023
1 parent 2bb7ee4 commit 9d512a1
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions scripts/build-upload-a-docker-image.sh
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,6 @@ docker buildx build --output "${PUSHTAG}" \
echo "Finished building${upload_flag} ${component_name} =============="

df -h /
docker buildx prune --all --verbose
docker system prune
docker buildx prune --all --verbose --force
docker system prune --force
df -h /

0 comments on commit 9d512a1

Please sign in to comment.