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

Update which Docker container can be used? #11

Closed
blipp opened this issue Feb 3, 2021 · 3 comments
Closed

Update which Docker container can be used? #11

blipp opened this issue Feb 3, 2021 · 3 comments

Comments

@blipp
Copy link

blipp commented Feb 3, 2021

The website currently recommends

For the lazy: Docker

Every night, we automatically build the projecteverest/everest Docker image with everything already built and verified, for you to directly pull from the Docker Hub. If you have Docker installed on your machine, then you can pull the image using the usual command:

docker pull projecteverest/everest-windows-nt

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?

@tahina-pro
Copy link
Member

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!

tahina-pro added a commit to project-everest/everest that referenced this issue Feb 4, 2021
@tahina-pro
Copy link
Member

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.

@tahina-pro
Copy link
Member

tahina-pro commented Mar 26, 2021

@nikswamy just uploaded an updated home page (9472184), which incorporates changes from b73633e and 0af8cb8 updating the documentation on Linux and Windows Docker images accordingly.

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

2 participants