This page is mainly intended for members of a release team who want to verify that they have built a tarball that will work for users. It could also be used by anybody else who wants to make sure a particular Evergreen tarball will work.

A huge thanks to Blake for creating this docker workflow!

1. Make sure that docker (or podman, if you prefer) and git are installed on your computer.
2. git clone https://github.com/mcoia/eg-docker.git
3. cd eg-docker/generic-tarball
4. Copy the tarball you wish to test into this generic-tarball directory.
5. Edit the vars.yml file. There is a line that says evergreen_version. Change this version to match the Evergreen version of your tarball.
6. docker build –add-host public.localhost:127.0.1.2 –add-host public:127.0.1.2 –add-host private.localhost:127.0.1.3 –add-host private:127.0.1.3 . -t eg :tarball-testing (this will take several minutes)
7. docker run -it -p 80:80 -p 443:443 -p 210:210 -p 6001:6001 -p 32:22 -p 5433:5432 -h app.evergreen.com –name my-testing-eg-tarball eg:tarball-testing (this will also take several minutes)
8. In your browser, go to http://localhost and confirm that the public catalog and staff catalog are working
9. In a new terminal window, run the automated tests with docker exec -it my-testing-eg-tarball ansible-playbook -e hosts=127.0.0.1 /egconfigs/run_tests.yml. It will give a short report at the end. ok, changed, skipped, and ignored items are expected, but failed means that one or more of our automated tests failed on the copy of the code within your tarball, which likely merits further investigation. Try running that test by itself to try to isolate the issue.
10. In your first terminal window, press Ctrl+C to stop the docker container.
11. docker rm my-testing-eg-tarball