Run myapp container in privileged mode (#103)

* Run myapp container in privileged mode

Windows may require myapp container to run in privileged mode to avoid Operation not permitted when preserving times (V. #102)

* Commented privileged mode setting

Updated myapp settings by commenting out 'privileged' parameter. (Privileged mode could be required under some circumstances in Windows, but should be avoided if possible.)

* Added help for users if myapp not up under Windows

Updated README.md so users are able to troubleshoot launch under Windows
This commit is contained in:
LSaraguA
2019-05-30 08:42:51 +02:00
committed by Andrés Bono
parent db742885c2
commit 3ec75f4d5a
2 changed files with 5 additions and 0 deletions

View File

@@ -86,6 +86,10 @@ Among other things, the above command creates a container service, named `myapp`
After the artisan application server has been launched in the `myapp` service, visit http://localhost:3000 in your favorite web browser and you'll be greeted by the default Laravel welcome page.
> **Note**
>
> If no application available at http://localhost:3000 and you're running Docker on Windows, you might need to uncomment `privileged` setting for `myapp` container. Later, re-launch the Laravel application development environment as stated before.
In addition to the Laravel Development Container, the [docker-compose.yml](https://raw.githubusercontent.com/bitnami/bitnami-docker-laravel/master/docker-compose.yml) file also configures a MariaDB service to serve as the database backend of your Laravel application.
## Executing commands

View File

@@ -23,3 +23,4 @@ services:
- 3000:3000
volumes:
- ./:/app
# privileged: true # Privileged mode could be required to run this container under Windows