Commit Graph

410402 Commits

Author SHA1 Message Date
Sameer Naik cd31c73eb7 Run install script as executable 2015-10-08 19:30:25 +05:30
Sameer Naik aaefc850b2 Merge pull request #4 from sameersbn/fix-install-script-execution
Run install script as executable
2015-10-08 19:29:28 +05:30
Sameer Naik b80865b6d3 Run install script as executable 2015-10-08 19:28:38 +05:30
Sameer Naik d4af9015d8 use the `entrypoint.sh` script from the base image 2015-10-08 19:23:45 +05:30
Sameer Naik a64fda3c8f the base image prints the welcome page by default 2015-10-08 19:23:45 +05:30
Sameer Naik b713240b1d append `EXTRA_OPTIONS` to command only if it is defined 2015-10-08 19:23:45 +05:30
Sameer Naik 9847548f1f moved `bitnami-utils-custom.sh` and `entrypoint.sh` to `rootfs/` directory 2015-10-08 19:23:45 +05:30
Sameer Naik d5f49c9c98 added circuit breaker logic for frequent and repeated failures 2015-10-08 19:23:45 +05:30
Sameer Naik b78a2124c6 added `mariadb-logs` service to tail the `mysqld.bin` logs 2015-10-08 19:23:45 +05:30
Sameer Naik 09b1ba287d moved most of the mariadb initialization and setup login into `01-bitnami-mariadb` 2015-10-08 19:23:45 +05:30
Sameer Naik 89a56c6240 specify `mysqld.bin` as the default command 2015-10-08 19:23:45 +05:30
Sameer Naik a3f80f88b2 do not start the mariadb service if user specifies a custom command 2015-10-08 19:23:45 +05:30
Sameer Naik 90361a7d0b removed pointless if condition from entrypoint.sh script 2015-10-08 19:23:45 +05:30
Sameer Naik 5157d1fe06 added init script to perform sanity checks 2015-10-08 19:23:45 +05:30
Sameer Naik 8a48641480 renamed `01-initialize-configs` -> `02-bitnami-mariadb-initialize` 2015-10-08 19:23:45 +05:30
Sameer Naik d1b6492a8a bring down the container if the `mariadb/run` script returns an
unrecoverable error
2015-10-08 19:23:45 +05:30
Sameer Naik a4fc9cfd02 enable user to specify parameters to the mariadb server from the command line 2015-10-08 19:23:45 +05:30
Sameer Naik d63a182a52 added `initialize-configs` init script to populate the `conf/` volume
`mysql` client fails when it is started from the docker run command line
due to missing `my.cnf`. To workaround this issue, we populate the
`conf/` volume from a `cont-init.d/01-initialize-configs` scripts.
2015-10-08 19:23:45 +05:30
Sameer Naik c8d5ae842e create s6 service for starting mariadb server 2015-10-08 19:23:45 +05:30
Adnan Abdulhussein 17e8570766 Merge pull request #15 from bitnami/fix-install-script-execution
Run install script as executable
2015-10-08 13:23:54 +01:00
Adnan Abdulhussein f806f67df5 Merge pull request #10 from bitnami/fix-install-script-execution
Run install script as executable
2015-10-08 13:08:17 +01:00
Adnan Abdulhussein ad1c39f6be Merge pull request #17 from bitnami/fix-install-script-execution
Run install script as executable
2015-10-08 13:08:08 +01:00
Adnan Abdulhussein 17db0c2d9c Merge pull request #6 from bitnami/fix-install-script-execution
Run install script as executable
2015-10-08 13:07:54 +01:00
Adnan Abdulhussein 018fba7559 Merge pull request #14 from bitnami/fix-install-script-execution
Run install script as executable
2015-10-08 13:07:40 +01:00
Adnan Abdulhussein 1a8a716db2 Merge pull request #22 from bitnami/fix-install-script-execution
Run install script as executable
2015-10-08 13:07:33 +01:00
Adnan Abdulhussein 2211ac6107 Merge pull request #10 from bitnami/fix-install-script-execution
Run install script as executable
2015-10-08 12:58:36 +01:00
Adnan Abdulhussein eb328cec9f Merge pull request #5 from bitnami/fix-install-script-execution
Run install script as executable
2015-10-08 12:58:27 +01:00
Adnan Abdulhussein 0aaa8c66d4 Run install script as executable 2015-10-08 12:51:26 +01:00
Adnan Abdulhussein 2fe2ac81f8 Run install script as executable 2015-10-08 12:50:43 +01:00
Adnan Abdulhussein 18c44ae55c Run install script as executable 2015-10-08 12:50:05 +01:00
Adnan Abdulhussein 272d3c7a1e Run install script as executable 2015-10-08 12:49:29 +01:00
Adnan Abdulhussein f617946a49 Run install script as executable 2015-10-08 12:46:53 +01:00
Adnan Abdulhussein 2f60c9caf6 Run install script as executable 2015-10-08 12:45:57 +01:00
Adnan Abdulhussein 5f762cb066 Merge pull request #11 from bitnami/fix-install-script-execution
Run install script as executable
2015-10-08 12:44:48 +01:00
Adnan Abdulhussein d4b8765733 Run install script as executable 2015-10-08 12:44:28 +01:00
Adnan Abdulhussein a9f1e007c8 Run install script as executable 2015-10-08 12:43:43 +01:00
Adnan Abdulhussein 23c5b9b16d Run install script as executable 2015-10-08 12:41:04 +01:00
Alejandro Ruiz cde347770e Not use sh for running the scripts 2015-10-08 11:40:46 +00:00
Alejandro Ruiz 5507d1e12f Not use sh for running the scripts 2015-10-08 11:40:39 +00:00
Alejandro Ruiz fc2a5b5c21 Not use sh for running the scripts 2015-10-08 11:40:19 +00:00
Sameer Naik 629387cc79 Merge pull request #2 from sameersbn/remove-app-volume
removed `/app` volume from dockerfile
2015-10-07 00:04:33 +05:30
Sameer Naik 281c71cb9b removed `/app` volume from dockerfile
Specifying a volume at `/app` (in the Dockerfile) makes it difficult to
use this image as a base image for derived images. Due to this, we have
removed the `VOLUME` instruction that mounts `/app` as a volume.

The `/app` path continues to function like it did before. As a result if
you want to mount your php application into the container, mount your
application source at `/app` using `-v
/path/on/application/source:/app`.

One advantage of mounting/installing your application at `/app` is that
the image will automatically update the ownership of the
files/directories in `/app` so that it is accessible by the wildfly
server.
2015-10-06 23:57:58 +05:30
Sameer Naik 39c1c8269c Merge pull request #3 from sameersbn/remove-app-volume
removed `/app` volume from dockerfile
2015-10-06 23:55:08 +05:30
Sameer Naik 31c9762fa0 removed `/app` volume from dockerfile
Specifying a volume at `/app` (in the Dockerfile) makes it difficult to
use this image as a base image for derived images. Due to this, we have
removed the `VOLUME` instruction that mounts `/app` as a volume.

The `/app` path continues to function like it did before. As a result if
you want to mount your php application into the container, mount your
application source at `/app` using `-v
/path/on/application/source:/app`.

One advantage of mounting/installing your application at `/app` is that
the image will automatically update the ownership of the
files/directories in `/app` so that it is accessible by the tomcat
server.
2015-10-06 23:53:43 +05:30
Sameer Naik c1508b3ed4 Merge pull request #13 from sameersbn/4.1.1-0-r01
bump version 4.1.1-0-r01
2015-10-06 22:16:18 +05:30
Sameer Naik 1a2e86d9c7 bump version 4.1.1-0-r01 2015-10-06 22:08:56 +05:30
Sameer Naik 30230cea0f Merge pull request #12 from sameersbn/remove-app-volume
Remove app volume
2015-10-06 22:07:53 +05:30
Sameer Naik 6fd7ffd22a removed `/app` volume from dockerfile
Specifying a volume at `/app` (in the Dockerfile) makes it difficult to
use this image as a base image for derived images. Due to this, we have
removed the `VOLUME` instruction that mounts `/app` as a volume.

The `/app` path continues to function like it did before. As a result if
you want to mount your php application into the container, mount your
application source at `/app` using `-v
/path/on/application/source:/app`.
2015-10-06 22:03:14 +05:30
Sameer Naik d9317111a4 tests: added `--noproxy node` argument to `curl` 2015-10-06 21:51:16 +05:30
Adnan Abdulhussein 66292c8a48 Merge pull request #16 from bitnami/5.5.30
Update to 5.5.30-0
2015-10-06 13:30:03 +01:00