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

Using 'latest' for a few of docker images #56

Open
wawrzek opened this issue May 31, 2024 · 1 comment
Open

Using 'latest' for a few of docker images #56

wawrzek opened this issue May 31, 2024 · 1 comment

Comments

@wawrzek
Copy link

wawrzek commented May 31, 2024

Using the 'latest' tag in a docker image definition is a dangerous practice, especially if the that can point at unstable images. That's the case for both the 'geth' and the 'prysmctl' images.

The recent problem with prysmctl, related to inclusion of incoming Electra work, was mentioned in #55 or #49, but there are more example of user hitting unstable image (e.g. #41).

One of the recent changes to geth caused the Failed to get EIP-1559 fees issue (ethereum/go-ethereum#29898). I also notice problems similar to ethereum/go-ethereum#29880.

The solution is to lock the version of all images (at least the ones not using the stable tag).

@wawrzek
Copy link
Author

wawrzek commented May 31, 2024

Example of a fix: ivy-net#2

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

No branches or pull requests

1 participant