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.

Sign up for GitHub

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

Jump to bottom

Uninformative error when docker fails #179

Open
dlipovetsky opened this issue May 8, 2019 · 0 comments
Open

Uninformative error when docker fails #179

dlipovetsky opened this issue May 8, 2019 · 0 comments

Comments

@dlipovetsky
Copy link
Contributor 

# /opt/bin/nodeadm init --cfg /etc/nodeadm.yaml
INFO[0000] Setting masterConfiguration.api.bindPort to 6443 
FATA[0002] failed to run "docker load -i /var/cache/nodeadm/images/18d31d4ba9ad3d8eb6a5abf53d907fa7501cb0fd2f2703a2bab3197a9ad186cc.tar": exit status 1

The cause turned out to be a corrupted tarball:

# docker load -i /var/cache/nodeadm/images/18d31d4ba9ad3d8eb6a5abf53d907fa7501cb0fd2f2703a2bab3197a9ad186cc.tar
fe9a8b4f1dcc: Loading layer [==================================================>]  43.87MB/43.87MB
invalid diffID for layer 0: expected "sha256:fe9a8b4f1dccd77105b8423a26536ff756f1ee99fdcae6893eb737ae1c527c7a", got "sha256:980b894612821b59edd3580d5f4358ff828a4e2bdc70840a82ecdf45fcaba38c"

cctl should relay the error message along with the exit code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dlipovetsky