-
Notifications
You must be signed in to change notification settings - Fork 633
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
ci: fix docker test #2302
ci: fix docker test #2302
Conversation
I remember there was quite a protest from vz guys for bashisms as they don't have bash in the testing setup (?). Just for curiosity: is it also fixed by pre-initializing |
@0x7f454c46 I remember I was to tired with all these shellshit and replaced /bin/sh with /bin/bash everywhere, so bash is required to run tests. |
f65e10c
to
be9a9fa
Compare
c527e90
to
bd16e3e
Compare
Replace a recursive call with a loop. Reported-by: Andrei Vagin <[email protected]> Signed-off-by: Radostin Stoyanov <[email protected]>
bd16e3e
to
c04efaa
Compare
Checkpoint/restore with version 25.0.0-beta.1 fails with the following error: $ docker start --checkpoint=c1 cr Error response from daemon: failed to create task for container: content digest fdb1054b00a8c07f08574ce52198c5501d1f552b6a5fb46105c688c70a9acb45: not found: unknown Release notes: moby/moby#46816 Signed-off-by: Radostin Stoyanov <[email protected]>
c04efaa
to
1ccbfe4
Compare
Thanks for the note, I was not aware of it =) But I know for sure that we don't run |
The version of docker-ce on Ubuntu 20.04 has been recently updated to 25.0.0-beta.1. However, with this version
docker start --checkpoint
fails with the following error:As a workaround, we install the most recent stable version of docker-ce. In addition, to improve code readability, the recursive function call used for retrying container restoration has been replaced with a loop.