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
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,3 +21,8 @@ You can do this by following the steps below:
21
21
2. Once the configuration is done, you may now initialize runtimes from your private repository by doing `devstack init the_runtime_name`.
22
22
3. To download the latest runtimes in your repository, run `devstack download`.
23
23
24
+
## Running Docker Compose Commands
25
+
1. If your are greeted by `Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?` after running a command, this means that your docker or docker desktop is not running.
26
+
2. If you are greeted by `no configuration file provided: not found` after running a command, this means that your current directory doesn't have the docker-compose.yml file.
27
+
3. If you are greeted by `service "<service>" is not running container #1` after running the following services `redis`, `mysql`, `php`, `composer`, and `composer`, this means that the containers are not yet up. Do `devsatck up -d` to start.
28
+
4. If your are greeted by `Could not open input file: artisan` after running `devstack artisan`, this means that the current runtime you are running has no Laravel Artisan command or is not a Laravel project.
0 commit comments