Updated MariaDB references. Re-compiled Redmine using the latest Ruby

2026-03-04 06:47:25 +08:00 · 2016-05-13 18:52:13 +02:00
parent f78e35ebed
commit f5cb955249
3 changed files with 64 additions and 87 deletions
--- a/bitnami/redmine/Dockerfile
+++ b/bitnami/redmine/Dockerfile
@@ -1,24 +1,26 @@
-FROM gcr.io/stacksmith-images/ubuntu:14.04-r05
+FROM gcr.io/stacksmith-images/ubuntu:14.04-r07

 MAINTAINER Bitnami <containers@bitnami.com>

-# Additional modules required
-RUN bitnami-pkg install imagemagick-6.7.5-10-3 --checksum 617e85a42c80f58c568f9bc7337e24c03e35cf4c7c22640407a7e1e16880cf88
-RUN bitnami-pkg install mysql-libraries-10.1.11-1 --checksum de90c294a3319ab33f82d4af09d0f4942fcc831268344146b8347ce885d52c29
-RUN bitnami-pkg install mysql-client-10.1.11-1 --checksum 8dea362fbff8ac4cc0342d9e9b62c66498fd8be59ab2e106aefd085888b66b58
-RUN bitnami-pkg install base-functions-1.0.0-1 --checksum ddd7aea91e039e07b571d5f4e589bedb5a1ae241e625f4a06a64a7ede439c7b8
-
-# Runtime
-RUN bitnami-pkg install ruby-2.1.8-6 --checksum 174b666a3c98b30be17f60d85e873be7c194472d6a1c07ac43516d97223dca85
-ENV PATH=/opt/bitnami/ruby/bin:$PATH
-
-# Install application
 ENV BITNAMI_APP_NAME=redmine \
-    BITNAMI_APP_VERSION=3.2.1-3
-RUN bitnami-pkg unpack redmine-3.2.1-1 --checksum c1faac8c6b30fc61f0a7486605395ef852cfce6e6cbdca7cdbdfb2bfe2476234
+    BITNAMI_IMAGE_VERSION=3.2.1-r3 \
+    PATH=/opt/bitnami/ruby/bin:$PATH
+
+# Additional modules required
+RUN bitnami-pkg install ruby-2.1.9-2 --checksum d9a014bb284fe1bd181008aa7f78b70b5259a93014a175df0a7e42084b2e2dd4
+RUN bitnami-pkg install imagemagick-6.7.5-10-3 --checksum 617e85a42c80f58c568f9bc7337e24c03e35cf4c7c22640407a7e1e16880cf88
+RUN bitnami-pkg install mysql-libraries-10.1.13-0 --checksum 71ca428b619901123493503f8a99ccfa588e5afddd26e0d503a32cca1bc2a389
+RUN bitnami-pkg install mysql-client-10.1.13-1 --checksum e16c0ace5cb779b486e52af83a56367f26af16a25b4ab92d8f4293f1bf307107
+
+# Install redmine
+RUN bitnami-pkg unpack redmine-3.2.1-3 --checksum bbb8e84f40132d30351155d4ba1be191fa1decb00f8ba25d7d6d5496dee81ddc

-# Setting entry point
 COPY rootfs /
+
+VOLUME ["/bitnami/redmine"]
+
+EXPOSE 3000
+
 ENTRYPOINT ["/app-entrypoint.sh"]

 CMD ["harpoon", "start", "--foreground", "redmine"]
--- a/bitnami/redmine/README.md
+++ b/bitnami/redmine/README.md
@@ -24,26 +24,22 @@ version: '2'

 services:
  mariadb:
-    image: bitnami/mariadb:latest
-    volumes_from:
-      - mariadb_data
-
-  mariadb_data:
-    image: bitnami/mariadb:latest
-    entrypoint: 'true'
-
-  application:
-    image: bitnami/redmine:latest
-    ports:
-      - 80:3000
-    volumes_from:
-      - application_data
-
-  application_data:
-    image: bitnami/redmine:latest
+    image: 'bitnami/mariadb:latest'
    volumes:
-      - /bitnami/redmine
-    entrypoint: 'true'
+      - 'mariadb_data:/bitnami/mariadb'
+  application:
+    image: 'bitnami/redmine:latest'
+    ports:
+      - '80:3000'
+    volumes:
+      - 'redmine_data:/bitnami/redmine'
+    depends_on:
+      - mariadb
+volumes:
+  mariadb_data:
+    driver: local
+  redmine_data:
+    driver: local
 ```

 ### Run the application manually
@@ -74,42 +70,28 @@ Then you can access your application at http://your-ip/

 ## Persisting your application

-If you remove every container 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 are using docker-compose your data will be persistent as long as you don't remove `mariadb_data` and `application_data` containers. Those are data volume containers (See https://docs.docker.com/engine/userguide/containers/dockervolumes/ for more information). If you have run the containers manually or you want to mount the folders with persistent data in your host follow the next steps:
+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 are using docker-compose your data will be persistent as long as you don't remove `mariadb_data` and `application_data` data volumes. If you have run the containers manually or you want to mount the folders with persistent data in your host follow the next steps:

 > **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 persistent folders in the host using docker-compose

 This requires a sightly modification from the template previously shown:
-```yaml
+```
 version: '2'

-services:
  mariadb:
-    image: bitnami/mariadb:latest
-    volumes_from:
-      - mariadb_data
-
-  mariadb_data:
-    image: bitnami/mariadb:latest
-    entrypoint: 'true'
+    image: 'bitnami/mariadb:latest'
    volumes:
-      - /your/local/path/bitnami/mariadb/data:/bitnami/mariadb/data
-      - /your/local/path/bitnami/mariadb/conf:/bitnami/mariadb/conf
-
+      - '/path/to/your/local/mariadb_data:/bitnami/mariadb'
  application:
    image: bitnami/redmine:latest
    ports:
      - 80:3000
-    volumes_from:
-      - application_data
-
-  application_data:
-    image: bitnami/redmine:latest
    volumes:
-      - /your/local/path/bitnami/redmine:/bitnami/redmine
-    entrypoint: 'true'
-
+      - '/path/to/your/local/redmine_data:/bitnami/redmine'
+    depends_on:
+      - mariadb
 ```

 ### Mount persistent folders manually
@@ -125,7 +107,7 @@ In this case you need to specify the directories to mount on the run command. Th
 2. Start a MariaDB database in the previous network:

  ```
-  $ docker run -d --name mariadb -v /your/local/path/bitnami/mariadb/data:/bitnami/mariadb/data -v /your/local/path/bitnami/mariadb/conf:/bitnami/mariadb/conf --net=redmine_network bitnami/mariadb
+  $ docker run -d --name mariadb -v /your/local/path/bitnami/mariadb:/bitnami/mariadb --network=redmine_network bitnami/mariadb
  ```

  *Note:* You need to give the container a name in order to Redmine to resolve the host
@@ -133,7 +115,7 @@ In this case you need to specify the directories to mount on the run command. Th
 3. Run the Redmine container:

  ```
-  $ docker run -d -p 80:3000 --name redmine -v /your/local/path/bitnami/redmine:/bitnami/redmine --net=redmine_network bitnami/redmine
+  $ docker run -d -p 80:3000 --name redmine -v /your/local/path/bitnami/redmine:/bitnami/redmine --network=redmine_network bitnami/redmine
  ```

 # Upgrade this application
@@ -155,8 +137,8 @@ $ docker pull bitnami/redmine:latest

 4. Remove the currently running container

- * For docker-compose: `$ docker-compose rm -v redmine`
- * For manual execution: `$ docker rm -v redmine`
+ * For docker-compose: `$ docker-compose rm redmine`
+ * For manual execution: `$ docker rm redmine`

 5. Run the new image

@@ -175,14 +157,16 @@ application:
    - 80:3000
  environment:
    - REDMINE_PASSWORD=my_password
-  volumes_from:
-    - application_data
+  volumes:
+    - 'redmine_data:/bitnami/redmine'
+  depends_on:
+    - mariadb
 ```

 * For manual execution add a `-e` option with each variable and value:

 ```
- $ docker run -d -e REDMINE_PASSWORD=my_password -p 80:3000 --name redmine -v /your/local/path/bitnami/redmine:/bitnami/redmine --net=redmine_network bitnami/redmine
+ $ docker run -d -e REDMINE_PASSWORD=my_password -p 80:3000 --name redmine -v /your/local/path/bitnami/redmine:/bitnami/redmine --network=redmine_network bitnami/redmine
 ```

 Available variables:
@@ -206,9 +190,9 @@ To configure Redmine to send email using SMTP you can set the following environm

 This would be an example of SMTP configuration using a GMail account:

- * docker-compose:
+ * docker-compose: 

-```yaml
+```
  application:
    image: bitnami/redmine:latest
    ports:
@@ -218,14 +202,12 @@ This would be an example of SMTP configuration using a GMail account:
      - SMTP_PORT=587
      - SMTP_USER=your_email@gmail.com
      - SMTP_PASSWORD=your_password
-    volumes_from:
-      - application_data
 ```

- * For manual execution:
+ * For manual execution: 

 ```
- $ docker run -d -e SMTP_HOST=smtp.gmail.com -e SMTP_PORT=587 -e SMTP_USER=your_email@gmail.com -e SMTP_PASSWORD=your_password -p 80:3000 --name redmine -v /your/local/path/bitnami/redmine:/bitnami/redmine --net=redmine_network bitnami/redmine$ docker rm -v redmine
+ $ docker run -d -e SMTP_HOST=smtp.gmail.com -e SMTP_PORT=587 -e SMTP_USER=your_email@gmail.com -e SMTP_PASSWORD=your_password -p 80:3000 --name redmine -v /your/local/path/bitnami/redmine:/bitnami/redmine --network=redmine_network bitnami/redmine$ docker rm -v redmine
 ```

 # Backing up your application
--- a/bitnami/redmine/docker-compose.yml
+++ b/bitnami/redmine/docker-compose.yml
@@ -1,26 +1,19 @@
 version: '2'
-
 services:
  mariadb:
-    image: bitnami/mariadb:latest
-    volumes_from:
-      - mariadb_data
-
-  mariadb_data:
-    image: bitnami/mariadb:latest
-    entrypoint: 'true'
-
+    image: 'bitnami/mariadb:latest'
+    volumes:
+      - 'mariadb_data:/bitnami/mariadb'
  application:
-    image: bitnami/redmine:latest
+    image: 'bitnami/redmine:latest'
    ports:
-      - "80:3000"
-    volumes_from:
-      - application_data
+      - '80:3000'
+    volumes:
+      - 'redmine_data:/bitnami/redmine'
    depends_on:
      - mariadb
-
-  application_data:
-    image: bitnami/redmine:latest
-    volumes:
-      - /bitnami/redmine
-    entrypoint: 'true'
+volumes:
+  mariadb_data:
+    driver: local
+  redmine_data:
+    driver: local