From c7e5337da91f9ba38ce182234490d16a970439c6 Mon Sep 17 00:00:00 2001 From: hitodama Date: Wed, 15 Jun 2016 00:42:54 +0200 Subject: [PATCH] ... never type what you can copy + warning --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 54f3a5a..56641a8 100644 --- a/README.md +++ b/README.md @@ -62,22 +62,22 @@ development will be as convenient as a local installation. With the benefit that do not have to build ps4sdk yourself. However, the image is a bit large due to the clang tool-chain. ```bash -# Make sure newest container is used -docker pull ps4dev/ps4sdk +# Make sure newest container is used (only do this as needed because you will pull a new one for every commit) +docker pull ps4dev/elf-loader # Run docker for interactive development # It should not be used to store data (-rm will auto remove it after exit) # See volumes/-v on how to mount your code into the container -docker run (-v ... ) -rm -i -t ps4dev/ps4sdk bash +docker run (-v ... ) --rm -i -t ps4dev/ps4sdk bash ``` From there, you can clone the elf-loader and examples into your volume, build and use them. A stand alone elf-loader container is also available (but currently a bit large): ```bash -# Make sure newest container is used +# Make sure newest container is used (only do this as needed) docker pull ps4dev/elf-loader # Run the elf loader (listens on port 5350) -docker run -p 5350:5350 -rm ps4dev/elf-loader& +docker run -p 5350:5350 --rm ps4dev/elf-loader& # Stop elf loader docker kill $(docker ps -q -f ancestor=ps4dev/elf-loader) ```