Commit d59c362b authored by Chris Shantz's avatar Chris Shantz

Update README.md with changes from wiki notes.

parent 63fa36a0
......@@ -104,7 +104,7 @@ First we need to build the images, this takes at least 10 minutes or so to build
```
**Note** The first time you run this on a Windows machine, you may be asked to share C: drive and you may need to add a Windows Firewall permission. Click yes/okay for both.
Also **Note** that docker caches images, if you update wcms-docker from Git and there are changes to the Dockerfiles (or anything that gets built by them) for any container you will need to rebuild.
**Also Note** that docker caches images, if you update wcms-docker from Git and there are changes to the Dockerfiles (or anything that gets built by them) for any container you will need to rebuild.
To do this you should use "docker-compose build --no-cache" which builds the image from whatever Dockerfile is referenced in the docker-compose.yml. You will then need to do a "docker-compose up -d" for it to use the new builds.
On a Windows machine, before you start the containers you will need to start your Ubuntu Shell. Once it's started, and you've logged in you will need to go to the directory you cloned wcms-docker into.
......@@ -181,6 +181,15 @@ Each container is assigned a specfic port:
## Troubleshooting
If you are running Portainer and you get this error:
```bash
un\\\\docker.sock:/var/run/docker.sock"\nis not a valid Windows path'
ERROR: for portainer Cannot create container for service portainer: b'Mount denied:\nThe source path "\\\\var\\\\run\\\\docker.sock:/var/run/docker.sock"\nis not a valid Windows path'
Encountered errors while bringing up the project.
```
You will need to use Windows Powershell (as Admin) and enter:
```bash
$Env:COMPOSE_CONVERT_WINDOWS_PATHS=1
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment