Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Dockerfile - reuse NO_PROXY_CACHE env #7203

Merged
merged 5 commits into from
Jun 13, 2024
Merged

Conversation

tbenr
Copy link
Contributor

@tbenr tbenr commented Jun 11, 2024

Just noticed this.

reuse NO_PROXY_CACHE env

Signed-off-by: Enrico Del Fante <[email protected]>
Copy link
Member

@usmansaleem usmansaleem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -6,7 +6,7 @@ ENV NO_PROXY_CACHE="-o Acquire::BrokenProxy=true -o Acquire::http::No-Cache=true
# Update and install dependencies without using any cache
RUN apt-get update $NO_PROXY_CACHE && \
# $NO_PROXY_CACHE must not be used here or otherwise will trigger a hadolint error
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: we can remove the above comment as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there was an actual bug in my changes. Fixed and removed a redundant rm -rf

@macfarla macfarla merged commit dfe256e into hyperledger:main Jun 13, 2024
40 checks passed
macfarla added a commit that referenced this pull request Jun 13, 2024
macfarla added a commit to macfarla/besu that referenced this pull request Jun 13, 2024
macfarla added a commit that referenced this pull request Jun 13, 2024
@tbenr tbenr deleted the patch-1 branch June 13, 2024 06:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants