* Fix #3980 by reworking how integration tests are launched - We used OS path mounted into container path (it makes issues as on Windows we don’t have these paths) - Now use /dockerfiles path inside the container - add skip check for nightlies or it was downloading new images while testing the current nightly - add —rm for cleaning containers at the end of docker run - introduce of some asserts instead of custom checks - Fix windows issue (like path with spaces) - Fix teardown of che start tests Change-Id: I352d7c475796df641c1e34f461c55a76c897922d Signed-off-by: Florent BENOIT <fbenoit@codenvy.com> |
||
|---|---|---|
| .. | ||
| Dockerfile | ||
| README.md | ||
| build.sh | ||
README.md
Creating an Eclipse Che instance from a local directory
Build Docker container
$ build.sh (on Unix)
> build.bat (on Windows)
Run container
Check no docker Eclipse Che container is alive and kill it if any
$ docker ps -a
Clone a folder
$ git clone https://github.com/che-samples/web-java-spring-petclinic
Go into this checkout directory
$ cd web-java-spring-petclinic
Run script
docker run -v /var/run/docker.sock:/var/run/docker.sock \
-v "$PWD":"$PWD" --rm eclipse/che-file \
$PWD <init|up>
note: if Eclipse Che is already started, it does not handle yet this state