theodorosploumis
commented
8 years ago 1) You don't need to have a container running, you only need the executable (drush) to be available to the www files where drupal exists. Saying that you can use your local drush executable if you like (if it is a phar file) and avoid drush/drush image at all. Here is an example:
version: '2'
services:
drupal:
image: drupal:8.1.1-apache
container_name: drupal_apache
volumes:
# Mount local drush to your container.
- /usr/local/bin/drush:/drush/drushthen you can run:
# drush status on the created container
docker exec drupal_apache /drush/drush status2) Normally you could volume the drush executable from drush/drush image but you can't do this since mount is not allowed for files. To do so you can create your own image based on drush/drush. Here is a simple Dockerfile:
FROM drush/drush:8
# Move drush to a more generic path so it can be used with any image
RUN mkdir -p /drush && \
mv -f /usr/local/bin/drush /drush/drush
# Volume the drush path so we can use it with other containers
VOLUME /drush
# Change the entrypoint to match the new drush path
ENTRYPOINT ["/drush/drush", "status"]Create the new drush image:
docker build -t drush-volumed:8 .and here is the docker-compose.yml file using volumes from the new drush-volumed:8 image:
version: '2'
services:
drupal:
image: drupal:8.1.1-apache
container_name: drupal_8081
volumes:
- /var/www/html
volumes_from:
- drush_volumed
ports:
- '8081:80'
links:
- mysql
mysql:
image: mysql:5.5
container_name: mysql
environment:
- MYSQL_ROOT_PASSWORD=root
- MYSQL_DATABASE=drupal
- MYSQL_USER=drupal
- MYSQL_PASSWORD=drupal
drush_volumed:
image: drush-volumed:8
container_name: drush_volumedI am about to create a pull request for this as it is major and I think a lot of drupal developers will come to the same issue when they start using docker.
peperoni60
opdavies
sgarciafer
jubalm
james-nesbitt
leolandotan
dixhuit
elalemanyo
RobLoach
GuyPaddock
EnzoJURET
Hi
This is a more a documentation issue than anything else.
I've downloaded the image and run drush as a standalone container like described on the Readme page and it worked well. In order to go deeper, I want to understand how to link a drush container with others containers but unfortunately I have not been able to make it working.
In my docker-compose.yml file I have defined the following containers:
nginx: build: nginx-fpm links: - phpfpm ports: - "8080:80" volumes_from: - data phpfpm: build: php-5.6-fpm-custom volumes_from: - data - db db: image: mariadb volumes: - /var/run/mysqld - ./databases/active:/var/lib/mysql environment: MYSQL_ROOT_PASSWORD: password MYSQL_DATABASE: application data: image: busybox stdin_open: true volumes: - ./htdocs:/var/www/html drush: image: drush/drush volumes_from: - data - db links: - phpfpm - dbWhen starting all the containers, I can see Drush's container working, displaying the list of commands and them exiting.
I though the container would live as a normal container and would allow me to manage Drupal.
Maybe I did not understand the purpose of this repo or maybe this is due to my short experience with docker and docker-compose but I have not found how to use the repo with several containers. Could you give me a hint on how to achieve it ?
Thanks