Skip to content

Commit

Permalink
[DOCKER] Fixing docker-compose, and not running Runtime by default
Browse files Browse the repository at this point in the history
Former-commit-id: 7775e56
  • Loading branch information
AVSurfer123 committed Aug 27, 2020
1 parent 59df145 commit 091e443
Show file tree
Hide file tree
Showing 2 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion docker-compose.yml
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ services:
context: .
dockerfile: docker/Dockerfile
image: pierobotics/runtime:latest
command: bash -c "./runtime build && ./runtime run"
command: bash -c "./runtime build && tail -f /dev/null"
volumes:
# Changes in local runtime/ and container /root/runtime are synced
- .:/root/runtime
8 changes: 4 additions & 4 deletions docker/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,17 +22,17 @@ If you are on Windows/Mac, you will be using Docker Desktop which will already h

If you are just starting out and want to get into development quickly, go to the `runtime` folder and do

docker-compose run --rm runtime bash
docker-compose up -d

which will begin a bash shell in the Docker container. From there you can call `runtime run` and the other `runtime` commands mentioned in the root README. Also, in another terminal you can do
which will start the Docker container. Now you can do

docker-compose exec runtime bash

to run/test other things within the container. By default, the `runtime/` git folder and `/root/runtime` will be linked so changes in one place will also change in the other place.
to open up a bash terminal in the container. You can repeat this command to get however many bash terminals you want. From the container, you can then call `runtime run` and the other `runtime` commands mentioned in the root README. Additionally, the `runtime/` git folder and `/root/runtime` will be linked so changes in the container will also change on your machine.

## Stopping

To stop the container, just exit all your shells or do
To stop the container, do

docker-compose down

Expand Down

0 comments on commit 091e443

Please sign in to comment.