You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-2Lines changed: 10 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -27,10 +27,18 @@ Three additional containers are included that handle Composer, NPM, and Artisan
27
27
28
28
##Permissions Issues
29
29
30
-
If you encounter any issues with filesystem permissions while visiting your application or running a container command, try completing the following steps:
30
+
If you encounter any issues with filesystem permissions while visiting your application or running a container command, try completing one of the sets of steps below.
31
+
32
+
**If you are using your server or local environment as the root user:**
33
+
34
+
- Bring any container(s) down with`docker-compose down`
35
+
- Rename`docker-compose.root.yml` file to`docker-compose.root.yml`, replacing the previous one
36
+
- Re-build the containers by running`docker-compose build --no-cache`
37
+
38
+
**If you are using your server or local environment as a user that is not root:**
31
39
32
40
- Bring any container(s) down with`docker-compose down`
33
-
- In your terminal, run`export UID=$(id -u) &&export GID=$(id -g)`
41
+
- In your terminal, run`export UID=$(id -u)` and then`export GID=$(id -g)`
34
42
- Re-build the containers by running`docker-compose build --no-cache`
35
43
36
44
Then, either bring back up your container network or re-run the command you were trying before, and see if that fixes it.