{"id":267,"date":"2023-10-23T21:57:06","date_gmt":"2023-10-23T21:57:06","guid":{"rendered":"http:\/\/kinori.tech\/blog\/?p=267"},"modified":"2026-03-07T11:56:41","modified_gmt":"2026-03-07T11:56:41","slug":"laravel-sail-in-windows-with-docker-and-powershell","status":"publish","type":"post","link":"https:\/\/kinori.tech\/blog\/en\/2023\/10\/23\/laravel-sail-in-windows-with-docker-and-powershell\/","title":{"rendered":"Laravel + Sail in Windows with Docker and PowerShell."},"content":{"rendered":"\n
\n

Laravel Sail<\/a> is a light-weight command-line interface for interacting with Laravel’s default Docker development environment.<\/p>\nLaravel Sail – Laravel 10.x – The PHP Framework For Web Artisans<\/a><\/cite><\/blockquote>\n\n\n\n

For me, it was the answer to the issues I faced on my Mac laptop with Brew deciding it had to update my PHP and no easy way to stop it. However, I also have a Windows PC on which I sometimes work and was left in shock when I realized that it wasn’t that easy on Windows.<\/p>\n\n\n\n

The actual issue, in Linux, Windows or Mac, is that although Sail commands are executed inside the Docker image, you need PHP in your machine to do the initial composer install to get Laravel\/Sail. To avoid headaches, the PHP version must match the version expected by Laravel and the packages you are using. When managing multiple Laravel applications, handling the PHP versions can be complex and time-consuming. Enter docker.<\/p>\n\n\n\n

The benefit of docker, in this scenario, is that you can have a separate container for each Laravel application, each with its matching PHP version. The issue is that you have a chicken-and-egg problem; you need sail to create and start the container, but you need the container to run composer and install sail. The first part of this tutorial solves the chicken-egg problem.<\/p>\n\n\n\n

The second issue (more like an annoyance) is that since Sail is a bash tool, you will need to install a Linux Subsystem in your Windows machine and use it to run your Sail commands. The main issue with this approach is that IDEs cannot easily use the WSL terminal to run commands, resulting in having to switch between applications while working with Laravel apps. The second part of this tutorial introduces a native PowerShell version of Sail that can be used directly in a PowerShell terminal and\/or from within your IDE.<\/p>\n\n\n\n

Bootstrap the (new) Laravel application with Docker Compose<\/h2>\n\n\n\n

To solve the chicken-and-egg problem, we can use a bootstrap container with PHP, from which we can execute Composer<\/a>, the PHP dependency management tool. This container can be used to create a new Laravel project or to work on an existing one (e.g. in my case I pulled the code from a repository). You will use this container to run composer and populate the application’s vendor folder. Once the vendor folder is populated, you can use Laravel’s Sail.<\/p>\n\n\n\n

If you have an existing application, clone it (or get a copy) to your Windows machine:<\/p>\n\n\n

\nPS C:\\git> git clone git@laravel-app.git\nCloning into 'laravel-app'...\nPS C:\\git> cd laravel-app\nPS C:\\git\\laravel-app>\n<\/pre><\/div>\n\n\n
If you are starting a new Larvel application, create a new folder for it:<\/p>\n\n\n
\nPS C:\\git> mkdir laravel-app\n\n    Directory: C:\\git\n\nMode                 LastWriteTime         Length Name\n----                 -------------         ------ ----\nd----           9\/26\/2023  9:09 AM                laravel-app\n\nPS C:\\git> cd .\\laravel-app\\\nPS C:\\git\\laravel-app>\n<\/pre><\/div>\n\n\n
To avoid mixing the bootstrap files with your Laravel application files, create a folder called dev<\/kbd>:<\/p>\n\n\n
\nPS C:\\git\\laravel-app> mkdir dev\n\n    Directory: C:\\git\\laravel-app\n\nMode                 LastWriteTime         Length Name\n----                 -------------         ------ ----\nd----           9\/26\/2023 10:06 AM                dev\n\nPS C:\\git\\laravel-app> cd dev\nPS C:\\git\\laravel-app\\dev>\n<\/pre><\/div>\n\n\n
Next, you\u2019ll create the docker-compose.yml<\/kbd> file that will define the containerized environment with PHP. In this file, you\u2019ll set up a service named bootstrap<\/kbd>, which will be based on a custom Docker image built with a Dockerfile you\u2019ll set up later on. <\/p>\n\n\n\n
Create a new\u00a0docker-compose.yml<\/kbd>\u00a0file using your text editor of choice. Here,\u00a0notepad++\u00a0is used (I highly recommend NOT to use Windows’ Notepad because it does not like files without extension and will automatically add the txt extension if you don’t use one).<\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev> Start notepad++ docker-compose.yml\nPS C:\\git\\laravel-app\\dev>\n<\/pre><\/div>\n\n\n
Copy the following content to this file, and don\u2019t forget to replace the WWWGROUP<\/kbd> value with the result from the previous command:<\/p>\n\n\n
\nversion: "3.7"\n\nservices:\n  #Bootstrap Container\n  bootstrap:\n    build:\n      dockerfile: Dockerfile\n    extra_hosts:\n      - 'host.docker.internal:host-gateway'\n    ports:\n      - '${APP_PORT:-80}:80'\n    volumes:\n      - '..:\/var\/www\/html'\n    networks:\n      - sail\nnetworks:\n    sail:\n        driver: bridge\n<\/pre><\/div>\n\n\n
Save and close the file when you are done. If you are using notepad<\/kbd>, you can do that by pressing CTRL+S<\/kbd>, and then closing the app. <\/p>\n\n\n\n
The docker-compose.yml<\/kbd>\u00a0requires a Dockerfile (line 5). We use the Dockerfile to install a few PHP dependencies that are required to install Laravel, and the Composer executable. To avoid version issues, you need to modify the first line to match the PHP version required by the Laravel version<\/a> you are using. As opposed to Unix systems, docker in Windows will run your containers as root, not as your user in the host machine. So there is no need to create groups or users.<\/p>\n\n\n\n
Create a new Dockerfile<\/em> file using your text editor of choice (I am using notepad++).<\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev> Start notepad++ Dockerfile\nPS C:\\git\\laravel-app\\dev>\n<\/pre><\/div>\n\n
\nFROM php:8.1-fpm\n\n# Install system dependencies\nRUN apt-get update && apt-get install -y \\\n    git \\\n    curl \\\n    libpng-dev \\\n    libonig-dev \\\n    libxml2-dev \\\n    zip \\\n    unzip\n\n# Clear cache\nRUN apt-get clean && rm -rf \/var\/lib\/apt\/lists\/*\n\n# Install PHP extensions\nRUN docker-php-ext-install mbstring exif pcntl bcmath gd\n\n# Use the default production configuration\nRUN mv "$PHP_INI_DIR\/php.ini-production" "$PHP_INI_DIR\/php.ini"\n\n# Get latest Composer\nCOPY --from=composer:latest \/usr\/bin\/composer \/usr\/bin\/composer\n\n# Set working directory\nWORKDIR \/var\/www\/html\n<\/pre><\/div>\n\n\n
Save and close the file when you\u2019re done.  Windows does not like files without extensions, so it probably added “.txt” to your file when saving it. You can check and remove the extension if needed:<\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev> dir\n\n    Directory: C:\\git\\laravel-app\\dev\n\nMode                 LastWriteTime         Length Name\n----                 -------------         ------ ----\n-a---           9\/27\/2023  8:54 AM            366 docker-compose.yml\n-a---           9\/27\/2023  8:54 AM            720 Dockerfile.txt\n\nPS C:\\git\\laravel-app\\dev> mv .\\Dockerfile.txt Dockerfile\nPS C:\\git\\laravel-app\\dev> dir\n\n    Directory: C:\\git\\laravel-app\\dev\n\nMode                 LastWriteTime         Length Name\n----                 -------------         ------ ----\n-a---           9\/27\/2023  8:54 AM            366 docker-compose.yml\n-a---           9\/27\/2023  8:54 AM            720 Dockerfile\n<\/pre><\/div>\n\n\n
Next, you can bring your environment up with:<\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev> docker-compose up -d\n<\/pre><\/div>\n\n\n
This command will execute Docker Compose in detached mode<\/em>, which means it will run in the background. The first time you bring an environment up with a custom image, Docker Compose will automatically build the image for you before creating the required containers. This might take a few moments to finish. You\u2019ll see output similar to this:<\/p>\n\n\n
\n[+] Building 61.2s (16\/16) FINISHED                                                                      docker:default\n => [bootstrap internal] load build definition from Dockerfile                                                     0.0s\n => => transferring dockerfile: 795B                                                                               0.0s\n => [bootstrap internal] load .dockerignore                                                                        0.0s\n => => transferring context: 2B                                                                                    0.0s\n => [bootstrap internal] load metadata for docker.io\/library\/php:8.1-fpm                                           0.5s\n => [bootstrap internal] load metadata for docker.io\/library\/composer:latest                                       0.5s\n => CACHED [bootstrap stage-0  1\/10] FROM docker.io\/library\/php:8.1-fpm@sha256:d94c26a8632c0c87557dbb1839a395fa5b  0.0s\n => => resolve docker.io\/library\/php:8.1-fpm@sha256:d94c26a8632c0c87557dbb1839a395fa5b69b5f8fbd944b025c5a5783a0dc  0.0s\n => CACHED [bootstrap] FROM docker.io\/library\/composer:latest@sha256:1ac7a547cb88acb0de62663b70f2b3d80ad273552882  0.0s\n => [bootstrap stage-0  3\/10] RUN apt-get update && apt-get install -y     git     curl     libpng-dev     libon  17.3s\n => [bootstrap stage-0  4\/10] RUN apt-get clean && rm -rf \/var\/lib\/apt\/lists\/*                                     0.5s\n => [bootstrap stage-0  5\/10] RUN docker-php-ext-install mbstring exif pcntl bcmath gd                            40.1s\n => [bootstrap stage-0  6\/10] RUN mv "\/usr\/local\/etc\/php\/php.ini-production" "\/usr\/local\/etc\/php\/php.ini"          0.4s\n => [bootstrap stage-0  7\/10] COPY --from=composer:latest \/usr\/bin\/composer \/usr\/bin\/composer                      0.1s\n => [bootstrap stage-0  8\/10] RUN groupadd --force -g 1001 sail                                                    0.5s\n => [bootstrap stage-0  9\/10] RUN useradd -ms \/bin\/bash --no-user-group -g 1001 -u 1337 sail                       0.8s\n => [bootstrap stage-0 10\/10] WORKDIR \/var\/www\/html                                                                0.0s\n => [bootstrap] exporting to image                                                                                 0.5s\n => => exporting layers                                                                                            0.5s\n => => writing image sha256:21d0a638d751287c2dc7361b8c04f3563d3c96338cef44c4c98cffde5f91f108                       0.0s\n => => naming to docker.io\/library\/dev-bootstrap                                                                   0.0s\ntime="2023-09-27T09:22:39-06:00" level=warning msg="Found orphan containers ([dev-app-1]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up."\n[+] Running 1\/1\n \u2714 Container dev-bootstrap-1  Started\n<\/pre><\/div>\n\n\n
You can verify that your environment is up and running with:<\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev> docker-compose ps\nNAME              IMAGE           COMMAND                           SERVICE     CREATED         STATUS         PORTS\ndev-bootstrap-1   dev-bootstrap   "docker-php-entrypoint php-fpm"   bootstrap   2 minutes ago   Up 2 minutes   0.0.0.0:80->80\/tcp, 9000\/tcp\nPS C:\\git\\laravel-app\\dev>\n<\/pre><\/div>\n\n\n
Once the bootstrap service is up, you can run Composer, to bootstrap an existing or new Laravel application. In order to do that, you\u2019ll use docker compose exec to run commands on the bootstrap service, where PHP is installed.<\/p>\n\n\n\n
New Laravel Application<\/h3>\n\n\n\n
For a new Laravel application, the following command will use Docker Compose to execute composer create-project<\/kbd>, which will bootstrap a fresh installation of Laravel based on the laravel\/laravel<\/kbd> package:<\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev>docker-compose exec bootstrap composer create-project laravel\/laravel --prefer-dist temp\nCreating a "laravel\/laravel" project at ".\/temp"\nInfo from https:\/\/repo.packagist.org: #StandWithUkraine\nInstalling laravel\/laravel (v10.2.6)\n  - Installing laravel\/laravel (v10.2.6): Extracting archive\nCreated project in \/var\/www\/html\/temp\n> @php -r "file_exists('.env') || copy('.env.example', '.env');"\nLoading composer repositories with package information\nUpdating dependencies\nLock file operations: 110 installs, 0 updates, 0 removals\n...\n82 packages you are using are looking for funding.\nUse the `composer fund` command to find out more!\n> @php artisan vendor:publish --tag=laravel-assets --ansi --force\n\n   INFO  No publishable resources for tag [laravel-assets].\n\nNo security vulnerability advisories found.\n> @php artisan key:generate --ansi\n\n   INFO  Application key set successfully.\n<\/pre><\/div>\n\n\n
The Laravel application will be created in the temp<\/em> folder, so next, you will have to move the files to the root of your laravel-app<\/kbd> folder:<\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev> cd ..\nPS C:\\git\\laravel-app> Copy-Item -Path "temp\\*" -Destination ".\\" -Recurse\nPS C:\\git\\laravel-app> Remove-Item -Recurse -Force temp\nPS C:\\git\\laravel-app> dir\n\n    Directory: C:\\git\\laravel-app\n\nMode                 LastWriteTime         Length Name\n----                 -------------         ------ ----\nd----           9\/27\/2023  1:36 PM                app\nd----           9\/27\/2023  1:36 PM                bootstrap\nd----           9\/27\/2023  1:36 PM                config\nd----           9\/27\/2023  1:36 PM                database\nd----           9\/27\/2023  9:21 AM                dev\nd----           9\/27\/2023  1:36 PM                public\nd----           9\/27\/2023  1:36 PM                resources\nd----           9\/27\/2023  1:36 PM                routes\nd----           9\/27\/2023  1:36 PM                storage\nd----           9\/27\/2023  1:36 PM                tests\nd----           9\/27\/2023  1:36 PM                vendor\n-a---           8\/10\/2023  1:19 AM            258 .editorconfig\n-a---           9\/27\/2023  1:36 PM           1148 .env\n-a---           8\/10\/2023  1:19 AM           1097 .env.example\n-a---           8\/10\/2023  1:19 AM            186 .gitattributes\n-a---           8\/10\/2023  1:19 AM            243 .gitignore\n-a---           8\/10\/2023  1:19 AM           1686 artisan\n-a---           8\/10\/2023  1:19 AM           1882 composer.json\n-a---           9\/27\/2023  1:31 PM         296013 composer.lock\n-a---           8\/10\/2023  1:19 AM            248 package.json\n-a---           8\/10\/2023  1:19 AM           1084 phpunit.xml\n-a---           8\/10\/2023  1:19 AM           4158 README.md\n-a---           8\/10\/2023  1:19 AM            263 vite.config.js\n\n<\/pre><\/div>\n\n\n
The next step is for you to install Sail (remember that the docker-compose commands must be executed from the dev<\/em> folder):<\/p>\n\n\n
\nPS C:\\git\\laravel-app> cd dev\nPS C:\\git\\laravel-app\\dev> docker-compose exec bootstrap composer require laravel\/sail --dev\nInfo from https:\/\/repo.packagist.org: #StandWithUkraine\n.\/composer.json has been updated\nRunning composer update laravel\/sail\n...\nUsing version ^1.25 for laravel\/sail\n<\/pre><\/div>\n\n\n
After Sail has been installed, you may run the sail:install<\/kbd> Artisan command. This command will publish Sail’s docker-compose.yml<\/kbd> file to the root of your application. You need to select the services you want to install:<\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev> docker-compose exec bootstrap php artisan sail:install\n\n \u250c Which services would you like to install? \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510\n \u2502 mariadb                                                      \u2502\n \u2502 redis                                                        \u2502\n \u2502 meilisearch                                                  \u2502\n \u2502 mailpit                                                      \u2502\n \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518\n\nSail scaffolding installed successfully.\nPS C:\\git\\laravel-app\\dev>\n<\/pre><\/div>\n\n\n
Existing Laravel Application<\/h3>\n\n\n\n
For an existing Laravel application, the following command will use Docker Compose to execute composer install<\/kbd>, which will install Laravel with all the dependencies defined in the composer.json<\/kbd> file.:<\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev> docker-compose exec bootstrap composer install\nInstalling dependencies from lock file (including require-dev)\nVerifying lock file contents can be installed on current platform.\nPackage operations: 191 installs, 0 updates, 0 removals\n...\nGenerating optimized autoload files\n> Illuminate\\Foundation\\ComposerScripts::postAutoloadDump\n> @php artisan package:discover --ansi\n...\n126 packages you are using are looking for funding.\nUse the `composer fund` command to find out more!\n<\/pre><\/div>\n\n\n
Depending on the packages you are using on the Laravel project, it is possible that the composer command will fail due to missing PHP extensions. For example, this project uses the *intl* package which is missing. <\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev>docker-compose exec bootstrap composer install\nInstalling dependencies from lock file (including require-dev)\nVerifying lock file contents can be installed on current platform.\nYour lock file does not contain a compatible set of packages. Please run composer update.\n\n  Problem 1\n    - Root composer.json requires PHP extension ext-intl * but it is missing from your system. Install or enable PHP's intl extension.\n...\n<\/pre><\/div>\n\n\n
As pointed out by the error, the reason for failure can be either because there is a missing PHP extension (not installed) or it has not been enabled in the PHP configuration. <\/p>\n\n\n\n
Installing additional  PHP packages<\/h3>\n\n\n\n
In order to install a missing PHP package, you need to modify the docker file provided previously. For this, you must modify the RUN docker-php-ext-install<\/kbd> command and add missing extensions. In this case, you will need to add the intl<\/kbd> extension. Open the Docker file and modify line 19 (just after the # Install PHP extensions<\/kbd> comment):<\/p>\n\n\n
\nRUN docker-php-ext-install mbstring exif pcntl bcmath gd intl\n<\/pre><\/div>\n\n\n
Since you need to modify the container, you need Docker to create it again. So first, you need to delete it. Open your Docker desktop app, select the Containers view in the left pane. Find the dev-bootstrap container and delete it.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Next, select the Images view in the left pane, and delete the dev\/bootstrap<\/kbd> image:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Finally, you need to create the container again and run the composer install command:<\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev> docker-compose up -d\nPS C:\\git\\eventastic\\web\\dev> docker-compose up -d\n[+] Building 110.7s (15\/15) FINISHED                                                                     docker:default\n...\n => [bootstrap stage-0 4\/9] RUN docker-php-ext-install mbstring exif pcntl bcmath gd intl                        106.9s\n...\nPS C:\\git\\laravel-app\\dev>docker-compose exec bootstrap composer install\nInstalling dependencies from lock file (including require-dev)\nVerifying lock file contents can be installed on current platform.\nYour lock file does not contain a compatible set of packages. Please run composer update.\n\n  Problem 1\n    - openspout\/openspout is locked to version v4.15.0 and an update of this package was not requested.\n    - openspout\/openspout v4.15.0 requires ext-zip * -> it is missing from your system. Install or enable PHP's zip extension.\n\n<\/pre><\/div>\n\n\n
So, the intl<\/kbd> package error is gone, but the command still fails due to the zip package. You need to repeat the previous steps till no more errors due to missing packages are found. <\/p>\n\n\n\n
NOTE<\/summary>\n
Additional PHP packages can require additional system libraries. When adding a PHP package, make sure to search the forums to determine if additional system libraries are needed. In this case, the RUN apt-get update && apt-get install -y \\ also needs to be modified in order to install the additional system libraries.<\/p>\n<\/details>\n\n\n\n
The second type of issue can be related to the required extension not enabled in the PHP configuration. In this case, we need to modify the php.ini<\/kbd> file. Although it is technically possible to directly edit the php.ini<\/kbd> file in the Docker container, it can be easier to modify the file in the Windows host. For this, we need to copy the php.ini<\/kbd> file from the container to the host machine. The easiest way to do this is to use the docker cp<\/kbd> command.  You will first need to get the name of your bootstrap container. For this, you can use the docker ps<\/kbd> command.<\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev> docker ps\nCONTAINER ID   IMAGE           COMMAND                  CREATED          STATUS          PORTS                          NAMES\n7598a58575ab   dev-bootstrap   "docker-php-entrypoi\u2026"   12 seconds ago   Up 10 seconds   0.0.0.0:80->80\/tcp, 9000\/tcp   dev-bootstrap-1\n<\/pre><\/div>\n\n\n
In this case, the container name is dev-bootstrap-1<\/kbd>. The other piece of information you need, is the destination path in the Windows host. You can use the pwd<\/kbd> command to do this. <\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev> $pwd.path\nC:\\git\\laravel-app\\dev\n<\/pre><\/div>\n\n\n
Next, you will use the cp command to copy the php.ini file to the Windows host. Three pieces of information are used in the command. First, the name of the docker container must be replaced with your specific value. Second, the location of the php.ini<\/kbd> file is specific to the fpm Docker images. Third, the file destination depends on where your project is located in the Windows host. <\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev> docker cp dev-bootstrap-1:\/usr\/local\/etc\/php\/php.ini C:\\git\\laravel-app\\dev\nSuccessfully copied 75.3kB to C:\\git\\laravel-app\\dev\n<\/pre><\/div>\n\n\n
Once you know what to change and made the changes, you can copy the php.ini file back to the container. For that, you need to invert the order of the cp arguments:<\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev> docker cp  C:\\git\\laravel-app\\dev\\php.ini dev-bootstrap-1:\/usr\/local\/etc\/php\nSuccessfully copied 75.3kB to dev-bootstrap-1:\/usr\/local\/etc\/php\n<\/pre><\/div>\n\n\n
For extension added via the Dockerfile using the docker-php-ext-install<\/kbd> there is no need to edit the php.ini file, as the extensions are enabled using the PHP config extension mechanism.<\/p>\n\n\n\n
Switching to Development<\/h2>\n\n\n\n
One you have bootstrapped your laravel application you can turn down your bootstrap container.<\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev> docker-compose down\n[+] Running 2\/2\n  Container dev-bootstrap-1 Removed 1.4s\n  Network dev_sail Removed\n<\/pre><\/div>\n\n\n
You no longer need the image, so you can go to your Docker panel an delete it. You can also delete the dev <\/kbd>folder.<\/p>\n\n\n\n
Native Sail via PowerShell<\/h2>\n\n\n\n
Laravel Sail<\/a> is available in Windows by using the WSL2. However, that means that you will need some extra work to configure your IDE to integrate with WSL. To avoid the hassle, and for cases where your IDE does not play nice with WSL2, I have written a PowerShell version of Sail called Jib<\/a>. To start using it, all you need to do is to install the script:<\/p>\n\n\n
\nPS> Install-Script -Name Jib\n<\/pre><\/div>\n\n\n
If it is the first time you are installing scripts from the PowerShell Gallery, it is possible that you get a warning about configuring your PATH so installed scripts are available globally. <\/p>\n\n\n\n
If you want to use Jib, you would need to run the installed script every time you open a PowerShell terminal. In order for Jib to be available in all your sessions, you add the script to your PowerShell profile. Windows creates the $PROFILE environment variable to point to the current user profile. You can open it with Notepad++ to edit it (if it does not exist, Notepad++ will ask you if you want to create the file):<\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev>Start notepad++ $profile\n<\/pre><\/div>\n\n\n
Edit the profile PS file to load the Jib script. You can add this line to the end of the profile:<\/p>\n\n\n
\n...\n$Path = Split-Path $Profile\n. $Path\\Scripts\\Jib.ps1\n<\/pre><\/div>\n\n\n
After saving the changes, go back to the PowerShell terminal and reload your profile:<\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev>. $profile\n<\/pre><\/div>\n\n\n
It is possible that you get an error message while reloading the profile: Management_Install.ps1<\/code> cannot be loaded because the execution of scripts is disabled on this system<\/kbd>. This stackoverflow post<\/a> provides a great summary of why and how to fix it. After your profile has been reloaded, you should be able to check if Jib is correctly loaded:<\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev> Get-Help Invoke-Jib\n\nNAME\n    Invoke-Jib\n\nSYNOPSIS\n    Jib is PowerShell replacement for the Laravel Sail bash\/shell command.\n ...\n\n<\/pre><\/div>\n\n\n
No you can use any of the supported Sail commands, for example, you can start your application:<\/p>\n\n\n
\nPS C:\\git\\laravel-app\\dev> Invoke-Jib up\nSetting the ENVIRONMENT from the '.env' file\nDeciding what docker compose to use.\nEnsure that Docker is running...\nDetermine if Sail is currently up...\nPass thru to docker-compose up\nExecuting command in container: docker compose up\n[+] Building 0.0s (0\/0)\n[+] Running 4\/0\n \u2714 Container laravel-app-mailhog-1       Created                                                                    0.0s\n \u2714 Container laravel-app-mariadb-1       Created                                                                    0.0s\n \u2714 Container laravel-app-redis-1         Created                                                                    0.0s\n \u2714 Container laravel-app-laravel.test-1  Created                                                                    0.0s\n...\nlaravel-app-laravel.test-1  |    INFO  Server running on [http:\/\/0.0.0.0:80].\nlaravel-app-laravel.test-1  |\nlaravel-app-laravel.test-1  |   Press Ctrl+C to stop the server\nlaravel-app-laravel.test-1  |\nlaravel-app-mailhog-1       | [APIv1] KEEPALIVE \/api\/v1\/events\n<\/pre><\/div>\n\n\n
Conclusion<\/h2>\n\n\n\n
You learned how to bootstrap a Laravel application using Docker, so we develop against a particular version of PHP in a Windows machine without requiring a local PHP installation (e.g. via XAMPP). You also installed the Jib PowerShell script, a Laravel Sail drop-in replacement, so we can interact with the Laravel container from the PowerShell terminal.<\/p>\n\n\n\n
I hope you find this information useful!<\/p>\n","protected":false},"excerpt":{"rendered":"
Laravel Sail is a light-weight command-line interface for interacting with Laravel’s default Docker development environment. Laravel Sail – Laravel 10.x – The PHP Framework For Web Artisans For me, it was the answer to the issues I faced on my Mac […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[22,19,21,23,20],"series":[],"class_list":["post-267","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-docker","tag-laravel","tag-php","tag-powershell","tag-sail"],"_links":{"self":[{"href":"https:\/\/kinori.tech\/blog\/wp-json\/wp\/v2\/posts\/267","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kinori.tech\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kinori.tech\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kinori.tech\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kinori.tech\/blog\/wp-json\/wp\/v2\/comments?post=267"}],"version-history":[{"count":44,"href":"https:\/\/kinori.tech\/blog\/wp-json\/wp\/v2\/posts\/267\/revisions"}],"predecessor-version":[{"id":408,"href":"https:\/\/kinori.tech\/blog\/wp-json\/wp\/v2\/posts\/267\/revisions\/408"}],"wp:attachment":[{"href":"https:\/\/kinori.tech\/blog\/wp-json\/wp\/v2\/media?parent=267"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kinori.tech\/blog\/wp-json\/wp\/v2\/categories?post=267"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kinori.tech\/blog\/wp-json\/wp\/v2\/tags?post=267"},{"taxonomy":"series","embeddable":true,"href":"https:\/\/kinori.tech\/blog\/wp-json\/wp\/v2\/series?post=267"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}