-
Notifications
You must be signed in to change notification settings - Fork 36
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
miner-genesis-init-container fail #11
Comments
@JPyml this might be a host specific issue, can you check if |
I just chmod and still the same issue : http://prntscr.com/j7t4zk |
this is probably due to the usage of hostPath which is very limited, i wonder if it makes sense to switch to local at some point
can you try |
I run my kubernetes with my root account but I have try with my commun user but i have still the same issue |
@JPyml ok, i'll try to reproduce the issue. thanks for the report |
It looks like this could be related to ethereum/go-ethereum#16464 The new docker image does not run with root permissions... Dropping back to v1.8.3 of the ethereum/go-client image works 👍 |
@Strydom good catch! thanks for the hint |
@MaximilianMeister In node.toml.erb, Line 50 there's a typo |
this is fixed in geth since release 1.8.6 see here the breaking PR has been reverted i've tested it on k8s 1.9.7 but I assume it is fixed as well on 1.10 @JPyml would be great if you can test it with a geth version >= 1.8.6 again, but i'll close the issue for now. feel free to reopen when it is still broken thanks for the help |
Hi,
I'm trying to deploy kuberneteth on my kubeadm cluster v1.10 but none miner containers can't run (it's in pending) because it wait for miner-genesis-init-container.
But my miner-genesis-init-container can't mkdir and touch in the volume mount because it haven't enough right : http://prntscr.com/j7sris
I don't know what i can do ?
The text was updated successfully, but these errors were encountered: