-
Notifications
You must be signed in to change notification settings - Fork 5
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
Update which Docker container can be used? #11
Comments
The Everest-Windows container is no longer up-to-date, since our internal CI stopped working due to moby/moby#41058 If the Everest-Linux container that you picked contains no binaries, then this is a bug in our CI system that sometimes unnecessarily pushes and overwrites existing images. We will look into that. Thank you for reporting! |
… upgrade is a no-op See bug project-everest/project-everest.github.io#11 reported by @blipp
I just fixed the CI system accordingly, so from now on all Everest Linux Docker images should be fully built. Please ping again if not. It now remains to change the documentation to explicitly state that, for now, the Everest Windows Docker images are stale because Cygwin is currently not as well supported within a Docker image as it used to be prior to June 1st, 2020. |
The website currently recommends
However, this particular container was last updated 8 months ago.
Instead, I tried everest-linux but it does not seem to have “everything already built”, at least there was no
FStar/bin/fstar.exe
in the container. Is this intentional, i.e., should the wording “everything already built and verified” be updated?The text was updated successfully, but these errors were encountered: