From e4bb17142cc9ffcf48e9b9c7eae08c995bdd9a12 Mon Sep 17 00:00:00 2001 From: H-Lo Date: Fri, 25 Oct 2019 13:41:01 -0700 Subject: [PATCH] Update container-README.md --- container-README.md | 28 ++++++++++++++++------------ 1 file changed, 16 insertions(+), 12 deletions(-) diff --git a/container-README.md b/container-README.md index f016dc4b..62794b60 100644 --- a/container-README.md +++ b/container-README.md @@ -14,39 +14,43 @@ The container is a basic install of alpine linux, so the image download is reasonably small On the container we have a few utilities and additionalsoftware that -prezto has core support for - -you can check it out in a snap by doing: - -docker pull hlecuanda/prezto-dev:latest +prezto has core support for, and you can check it out in a snap by doing: +```bash + docker pull hlecuanda/prezto-dev:latest +``` once you have the image, create a container from it with: +```bash docker run -it --rm -h prezto hlecuanda/prezto-dev:latest +``` -that will set you on a prompt withing the container with a +That will set you on a prompt within the container with a vanilla install of prezto. -a development and testing run can be achieved by mounting the stuff +A development and testing workflow can be achieved by mounting the stuff you're working on to the image's filesystem: +```bash docker run -it --rm -h prezto \ -v /local/path:/home/prezto \ -v /local/path/zdotdir:/home/preztoa \ -v /local/module-dev-src:/home/prezto/.zprezto/modules/yourmodulea \ hlecuanda/prezto-dev:latest +``` the third volume mapping is particularly interesting. you can -develop on your own machine and environnmen, and when spinning up the -container, your actual source is already in-plase asif installed on a -vanilla prezto install. +develop on your own machine and environnment, and when spinning up the +container, your actual source is already in-plase as if installed on a +vanilla prezto instance keep in mind that the container are ephemeral, unless you remove the ---rm option which will create new containers each time you run the +`--rm` option which will create new containers each time you run the command, but the changes to the filesystemwill persist on a container -file that you can later spin up again to re use. +file that you can later spin up again to re-use. I have found epehermeral containers to be most useful since you get an untainted, pristine environment for testing every time you spin up the container. +hope this turns out to be useful.