Bitnami Laravel Development Container
$ mkdir ~/myapp && cd ~/myapp $ curl -LO https://raw.githubusercontent.com/bitnami/bitnami-docker-laravel/master/docker-compose.yml $ docker-compose up
Why use Bitnami Images?
- Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
- With Bitnami images the latest bug fixes and features are available as soon as possible.
- Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
- Bitnami images are built on CircleCI and automatically pushed to the Docker Hub.
- All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading linux distribution.
The Bitnami Laravel Development Container has been carefully engineered to provide you and your team with a highly reproducible Laravel development environment. We hope you find the Bitnami Laravel Development Container useful in your quest for world domination. Happy hacking!
The quickest way to get started with the Bitnami Laravel Development Container is using docker-compose.
Begin by creating a directory for your Laravel application:
mkdir ~/myapp cd ~/myapp
Download the docker-compose.yml file in the application directory:
$ curl -LO https://raw.githubusercontent.com/bitnami/bitnami-docker-laravel/master/docker-compose.yml
Finally launch the Laravel application development environment using:
$ docker-compose up
Among other things, the above command creates a container service, named
myapp, for Laravel development and bootstraps a new Laravel application in the application directory. You can use your favorite IDE for developing the application.
If the application directory contained the source code of an existing Laravel application, the Bitnami Laravel Development Container would load the existing application instead of bootstrapping a new one.
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.
In addition to the Laravel Development Container, the docker-compose.yml file also configures a MariaDB service to serve as the database backend of your Laravel application.
Commands can be launched inside the
myapp Laravel Development Container with
docker-compose using the exec command.
execcommand was added to
docker-composein release 1.7.0. Please ensure that you're using
The general structure of the
exec command is:
$ docker-compose exec <service> <command>
<service> is the name of the container service as described in the
docker-compose.yml file and
<command> is the command you want to launch inside the service.
Following are a few examples of launching some commonly used Laravel development commands inside the
myapp service container.
$ docker-compose exec myapp php artisan list
List all registered routes:
$ docker-compose exec myapp php artisan route:list
Create a new application controller named
$ docker-compose exec myapp composer require phpmailer/phpmailer:5.2.*
If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:
- Host OS and version (
- Docker version (
- Docker info (
- Docker image version (
echo $BITNAMI_IMAGE_VERSIONinside the container)
- Steps to reproduce the issue.
Discussions are archived at bitnami-oss.slackarchive.io.
Copyright (c) 2015-2016 Bitnami
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
The working directory needs to be chown to 1000:1000. The container does not run as root by default and so gets permission denied creating the file structure. This should get added to your instructions.
Also it seems the current version of docker-compose does not have the exec command. Unless that's in a beta copy or something.