Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-04-02 15:27:45 +08:00
Code Issues Packages Projects Releases Wiki Activity

7.9.2-r1 release

Browse Source 
Removes VOLUME instruction from the Dockerfile
This commit is contained in:
Bitnami Bot
2017-07-04 17:08:16 +00:00
parent 9c102b5673
commit 08cebb9254
3 changed files with 38 additions and 73 deletions
Download Patch File Download Diff File Expand all files Collapse all files

94
bitnami/suitecrm/README.md
View File

@@ -1,5 +1,5 @@
[![CircleCI](https://circleci.com/gh/bitnami/bitnami-docker-suitecrm/tree/master.svg?style=shield)](https://circleci.com/gh/bitnami/bitnami-docker-suitecrm/tree/master)
[![Slack](http://slack.oss.bitnami.com/badge.svg)](http://slack.oss.bitnami.com)
[![Slack](https://img.shields.io/badge/slack-join%20chat%20%E2%86%92-e01563.svg)](http://slack.oss.bitnami.com)
[![Kubectl](https://img.shields.io/badge/kubectl-Available-green.svg)](https://raw.githubusercontent.com/bitnami/bitnami-docker-suitecrm/master/kubernetes.yml)
# What is SuiteCRM?
@@ -13,15 +13,15 @@ https://www.suitecrm.com/
## Docker Compose
```bash
$ curl -LO https://raw.githubusercontent.com/bitnami/bitnami-docker-suitecrm/master/docker-compose.yml
$ docker-compose up
$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-suitecrm/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d
```
## Kubernetes
> **WARNING**: This is a beta configuration, currently unsupported.
Get the raw URL pointing to the kubernetes.yml manifest and use kubectl to create the resources on your Kubernetes cluster like so:
Get the raw URL pointing to the `kubernetes.yml` manifest and use `kubectl` to create the resources on your Kubernetes cluster like so:
```bash
$ kubectl create -f https://raw.githubusercontent.com/bitnami/bitnami-docker-suitecrm/master/kubernetes.yml
@@ -37,7 +37,7 @@ $ kubectl create -f https://raw.githubusercontent.com/bitnami/bitnami-docker-sui
# Prerequisites
To run this application you need Docker Engine 1.10.0. Docker Compose is recommended with a version 1.6.0 or later.
To run this application you need [Docker Engine](https://www.docker.com/products/docker-engine) >= `1.10.0`. [Docker Compose](https://www.docker.com/products/docker-compose) is recommended with a version `1.6.0` or later.
# How to use this image
@@ -58,16 +58,14 @@ services:
environment:
- ALLOW_EMPTY_PASSWORD=yes
volumes:
- 'mariadb_data:/bitnami/mariadb'
- 'mariadb_data:/bitnami'
suitecrm:
image: 'bitnami/suitecrm:latest'
ports:
- '80:80'
- '443:443'
volumes:
- 'suitecrm_data:/bitnami/suitecrm'
- 'php_data:/bitnami/php'
- 'apache_data:/bitnami/apache'
- 'suitecrm_data:/bitnami'
depends_on:
- mariadb
@@ -76,10 +74,6 @@ volumes:
driver: local
suitecrm_data:
driver: local
apache_data:
driver: local
php_data:
driver: local
```
### Run the application manually
@@ -110,14 +104,14 @@ Then you can access your application at http://your-ip/
## Persisting your application
If you remove every container and volume all your data will be lost, and the next time you run the image the application will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
If you remove the container all your data and configurations will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
For persistence of the SuiteCRM deployment, the above examples define docker volumes namely `mariadb_data`, `suitecrm_data`, `apache_data` and `php_data`. The SuiteCRM application state will persist as long as these volumes are not removed.
For persistence you should mount a volume at the `/bitnami` path. Additionally you should mount a volume for [persistence of the MariaDB data](https://github.com/bitnami/bitnami-docker-mariadb#persisting-your-database).
The above examples define docker volumes namely `mariadb_data` and `suitecrm_data`. The SuiteCRM application state will persist as long as these volumes are not removed.
To avoid inadvertent removal of these volumes you can [mount host directories as data volumes](https://docs.docker.com/engine/tutorials/dockervolumes/). Alternatively you can make use of volume plugins to host the volume data.
> **Note!** If you have already started using your application, follow the steps on [backing](#backing-up-your-application) up to pull the data from your running container down to your host.
### Mount host directories as data volumes with Docker Compose
This requires a minor change to the `docker-compose.yml` template previously shown:
@@ -131,7 +125,7 @@ services:
environment:
- ALLOW_EMPTY_PASSWORD=yes
volumes:
- '/path/to/mariadb-persistence:/bitnami/mariadb'
- '/path/to/mariadb-persistence:/bitnami'
suitecrm:
image: 'bitnami/suitecrm:latest'
depends_on:
@@ -140,9 +134,7 @@ services:
- '80:80'
- '443:443'
volumes:
- '/path/to/suitecrm-persistence:/bitnami/suitecrm'
- '/path/to/php-persistence:/bitnami/php'
- '/path/to/apache-persistence:/bitnami/apache'
- '/path/to/suitecrm-persistence:/bitnami'
```
### Mount host directories as data volumes using the Docker command line
@@ -160,7 +152,7 @@ In this case you need to specify the directories to mount on the run command. Th
```bash
$ docker run -d --name mariadb -e ALLOW_EMPTY_PASSWORD=yes \
--net suitecrm-tier \
--volume /path/to/mariadb-persistence:/bitnami/mariadb \
--volume /path/to/mariadb-persistence:/bitnami \
bitnami/mariadb:latest
```
*Note:* You need to give the container a name in order to SuiteCRM to resolve the host
@@ -170,9 +162,7 @@ In this case you need to specify the directories to mount on the run command. Th
```bash
$ docker run -d --name suitecrm -p 80:80 -p 443:443 \
--net suitecrm-tier \
--volume /path/to/suitecrm-persistence:/bitnami/suitecrm \
--volume /path/to/apache-persistence:/bitnami/apache \
--volume /path/to/php-persistence:/bitnami/php \
--volume /path/to/suitecrm-persistence:/bitnami \
bitnami/suitecrm:latest
```
@@ -191,7 +181,15 @@ Bitnami provides up-to-date versions of MariaDB and SuiteCRM, including security
* For docker-compose: `$ docker-compose stop suitecrm`
* For manual execution: `$ docker stop suitecrm`
3. (For non-compose execution only) Create a [backup](#backing-up-your-application) if you have not mounted the suitecrm folder in the host.
3. Take a snapshot of the application state
```bash
$ rsync -a /path/to/suitecrm-persistence /path/to/suitecrm-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)
```
Additionally, [snapshot the MariaDB data](https://github.com/bitnami/bitnami-docker-mariadb#step-2-stop-and-backup-the-currently-running-container)
You can use these snapshots to restore the application state should the upgrade fail.
4. Remove the currently running container
@@ -204,8 +202,10 @@ Bitnami provides up-to-date versions of MariaDB and SuiteCRM, including security
* For manual execution ([mount](#mount-persistent-folders-manually) the directories if needed): `docker run --name suitecrm bitnami/suitecrm:latest`
# Configuration
## Environment variables
When you start the SuiteCRM image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the docker run command line. If you want to add a new environment variable:
When you start the SuiteCRM image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the docker run command line. If you want to add a new environment variable:
* For docker-compose add the variable name and value under the application section:
@@ -216,8 +216,6 @@ suitecrm:
- 80:80
environment:
- SUITECRM_PASSWORD=my_password
volumes_from:
- suitecrm_data
```
* For manual execution add a `-e` option with each variable and value:
@@ -226,9 +224,7 @@ suitecrm:
$ docker run -d -p 80:80 -p 443:443 --name suitecrm \
-e SUITECRM_PASSWORD=my_password \
--net suitecrm-tier \
--volume /path/to/suitecrm-persistence:/bitnami/suitecrm \
--volume /path/to/apache-persistence:/bitnami/apache \
--volume /path/to/php-persistence:/bitnami/php \
--volume /path/to/suitecrm-persistence:/bitnami \
bitnami/suitecrm:latest
```
@@ -281,47 +277,23 @@ This would be an example of SMTP configuration using a Gmail account:
-e SUITECRM_SMTP_USER=your_email@gmail.com \
-e SUITECRM_SMTP_PASSWORD=your_password
--net suitecrm-tier \
--volume /path/to/suitecrm-persistence:/bitnami/suitecrm \
--volume /path/to/apache-persistence:/bitnami/apache \
--volume /path/to/php-persistence:/bitnami/php \
--volume /path/to/suitecrm-persistence:/bitnami \
bitnami/suitecrm:latest
```
# Backing up your application
To backup your application data follow these steps:
1. Stop the running container:
* For docker-compose: `$ docker-compose stop suitecrm`
* For manual execution: `$ docker stop suitecrm`
2. Copy the SuiteCRM data folder in the host:
```bash
$ docker cp /path/to/suitecrm-persistence:/bitnami/suitecrm
```
# Restoring a backup
To restore your application using backed up data simply mount the folder with SuiteCRM data in the container. See [persisting your application](#persisting-your-application) section for more info.
# Contributing
We'd love for you to contribute to this container. You can request new features by creating an
[issue](https://github.com/bitnami/bitnami-docker-suitecrm/issues), or submit a [pull request](https://github.com/bitnami/bitnami-docker-suitecrm/pulls) with your contribution.
We'd love for you to contribute to this container. You can request new features by creating an [issue](https://github.com/bitnami/bitnami-docker-suitecrm/issues), or submit a [pull request](https://github.com/bitnami/bitnami-docker-suitecrm/pulls) with your contribution.
# Issues
If you encountered a problem running this container, you can file an
[issue](https://github.com/bitnami/bitnami-docker-suitecrm/issues). For us to provide better support,
be sure to include the following information in your issue:
If you encountered a problem running this container, you can file an [issue](https://github.com/bitnami/bitnami-docker-suitecrm/issues). For us to provide better support, be sure to include the following information in your issue:
- Host OS and version
- Docker version (`$ docker version`)
- Output of `$ docker info`
- Version of this container (`$ echo $BITNAMI_IMAGE_VERSION` inside the container)
- The command you used to run the container, and any relevant output you saw (masking any sensitive
information)
- The command you used to run the container, and any relevant output you saw (masking any sensitive information)
# Community
@@ -331,7 +303,7 @@ Discussions are archived at [bitnami-oss.slackarchive.io](https://bitnami-oss.sl
# License
Copyright 2016 Bitnami
Copyright 2016-2017 Bitnami
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.