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

Caching Docker layers seems to cause issues #8

Open
nano-o opened this issue Sep 18, 2020 · 3 comments
Open

Caching Docker layers seems to cause issues #8

nano-o opened this issue Sep 18, 2020 · 3 comments
Assignees

Comments

@nano-o
Copy link
Contributor

nano-o commented Sep 18, 2020

Hi Jared, thanks for setting up the CI!
I noticed the following issue: it succeeds on commit 4b8aa79 but fails on commit 53a61e6. The only different is that caching is disabled in the former.

@nano-o
Copy link
Contributor Author

nano-o commented Sep 25, 2020

I ran into the same issue on branch fix-keygen-patch, where caching is disabled. So it's something else, which seems exacerbated by caching. Last time, when I tried to diagnose it, I used https://github.com/mxschmitt/action-tmate to get a shell right before docker-compose run blst, and the problem didn't show up in the interactive shell...

@brianhuffman
Copy link

I just ran into this exact same problem while trying to run docker-compose build in a local clone of the blst-verification repo. A fix along the lines of GaloisInc/saw-script#1107 might be in order.

@nano-o
Copy link
Contributor Author

nano-o commented Mar 26, 2021

Okay, so if I understand correctly, the fix is to always prepend "apt-get update && " to any "apt-get install" command, in order to make sure it's not using a stale apt cache.

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

3 participants