Bitnami Docker Image for OpenCart
In order to unify the approaches followed for Bitnami containers and Bitnami Helm charts, we are moving the different bitnami/bitnami-docker-<container>
repositories to a single monorepo bitnami/containers
. Please follow bitnami/containers to keep you updated about the latest Bitnami images.
More information here: https://blog.bitnami.com/2022/07/new-source-of-truth-bitnami-containers.html
OpenCart is free open source ecommerce platform for online merchants. OpenCart provides a professional and reliable foundation from which to build a successful online store.
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-opencart/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d
Warning: This quick setup is only intended for development environments. You are encouraged to change the insecure default credentials and check out the available configuration options in the Environment Variables section for a more secure deployment.
DOCKER_CONTENT_TRUST=1
to verify the integrity of the images.Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami OpenCart Chart GitHub repository.
Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.
Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers in our docs.
Dockerfile
linksLearn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.
Subscribe to project updates by watching the bitnami/opencart GitHub repo.
The recommended way to get the Bitnami OpenCart Docker Image is to pull the prebuilt image from the Docker Hub Registry.
$ docker pull bitnami/opencart:latest
To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.
$ docker pull bitnami/opencart:[TAG]
If you wish, you can also build the image yourself.
$ docker build -t bitnami/opencart:latest 'https://github.com/bitnami/bitnami-docker-opencart.git#master:3/debian-11'
OpenCart requires access to a MySQL or MariaDB database to store information. We'll use the Bitnami Docker Image for MariaDB for the database requirements.
The main folder of this repository contains a functional docker-compose.yml
file. Run the application using it as shown below:
$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-opencart/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d
If you want to run the application manually instead of using docker-compose
, these are the basic steps you need to run:
$ docker network create opencart-network
$ docker volume create --name mariadb_data
$ docker run -d --name mariadb \
--env ALLOW_EMPTY_PASSWORD=yes \
--env MARIADB_USER=bn_opencart \
--env MARIADB_PASSWORD=bitnami \
--env MARIADB_DATABASE=bitnami_opencart \
--network opencart-network \
--volume mariadb_data:/bitnami/mariadb \
bitnami/mariadb:latest
$ docker volume create --name opencart_data
$ docker run -d --name opencart \
-p 8080:8080 -p 8443:8443 \
--env ALLOW_EMPTY_PASSWORD=yes \
--env OPENCART_DATABASE_USER=bn_opencart \
--env OPENCART_DATABASE_PASSWORD=bitnami \
--env OPENCART_DATABASE_NAME=bitnami_opencart \
--network opencart-network \
--volume opencart_data:/bitnami/opencart \
bitnami/opencart:latest
Then you can access the OpenCart storefront at http://your-ip/
. To access the administration area, login to http://your-ip/admin
.
Note: If you want to access your application from a public IP or hostname you need to configure OpenCart for it. You can handle it adjusting the configuration of the instance by setting the environment variable OPENCART_HOST
to your public IP or hostname.
If you remove the container all your data 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 you should mount a directory at the /bitnami/opencart
path. If the mounted directory is empty, it will be initialized on the first run. 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 the Docker volumes named mariadb_data
and opencart_data
. The OpenCart application state will persist as long as volumes are not removed.
To avoid inadvertent removal of volumes, you can mount host directories as data volumes. Alternatively you can make use of volume plugins to host the volume data.
This requires a minor change to the docker-compose.yml
file present in this repository:
mariadb:
...
volumes:
- - 'mariadb_data:/bitnami/mariadb'
+ - /path/to/mariadb-persistence:/bitnami/mariadb
...
opencart:
...
volumes:
- - 'opencart_data:/bitnami/opencart'
+ - /path/to/opencart-persistence:/bitnami/opencart
...
-volumes:
- mariadb_data:
- driver: local
- opencart_data:
- driver: local
NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID
1001
.
$ docker network create opencart-network
$ docker run -d --name mariadb \
--env ALLOW_EMPTY_PASSWORD=yes \
--env MARIADB_USER=bn_opencart \
--env MARIADB_PASSWORD=bitnami \
--env MARIADB_DATABASE=bitnami_opencart \
--network opencart-network \
--volume /path/to/mariadb-persistence:/bitnami/mariadb \
bitnami/mariadb:latest
$ docker run -d --name opencart \
-p 8080:8080 -p 8443:8443 \
--env ALLOW_EMPTY_PASSWORD=yes \
--env OPENCART_DATABASE_USER=bn_opencart \
--env OPENCART_DATABASE_PASSWORD=bitnami \
--env OPENCART_DATABASE_NAME=bitnami_opencart \
--network opencart-network \
--volume /path/to/opencart-persistence:/bitnami/opencart \
bitnami/opencart:latest
When you start the OpenCart 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:
docker-compose.yml
file present in this repository:opencart:
...
environment:
- OPENCART_PASSWORD=my_password
...
--env
option with each variable and value:$ docker run -d --name opencart -p 80:8080 -p 443:8443 \
--env OPENCART_PASSWORD=my_password \
--network opencart-tier \
--volume /path/to/opencart-persistence:/bitnami \
bitnami/opencart:latest
Available environment variables:
APACHE_HTTP_PORT_NUMBER
: Port to bind by Apache for HTTP. Default: 8080
APACHE_HTTPS_PORT_NUMBER
: Port to bind by Apache for HTTPS. Default: 8443
OPENCART_USERNAME
: OpenCart application username. Default: user
OPENCART_PASSWORD
: OpenCart application password. Default: bitnami
OPENCART_EMAIL
: OpenCart application email. Default: [email protected]
OPENCART_HOST
: OpenCart server hostname/address.OPENCART_ENABLE_HTTPS
: Whether to use HTTPS by default. Default: no.OPENCART_EXTERNAL_HTTP_PORT_NUMBER
: Port to used by OpenCart to generate URLs and links when accessing using HTTP. Default 80.OPENCART_EXTERNAL_HTTPS_PORT_NUMBER
: Port to used by OpenCart to generate URLs and links when accessing using HTTPS. Default 443.OPENCART_SKIP_BOOTSTRAP
: Whether to skip performing the initial bootstrapping for the application. Default: no
OPENCART_DATABASE_HOST
: Hostname for MariaDB server. Default: mariadb
OPENCART_DATABASE_PORT_NUMBER
: Port used by MariaDB server. Default: 3306
OPENCART_DATABASE_NAME
: Database name that OpenCart will use to connect with the database. Default: bitnami_opencart
OPENCART_DATABASE_USER
: Database user that OpenCart will use to connect with the database. Default: bn_opencart
OPENCART_DATABASE_PASSWORD
: Database password that OpenCart will use to connect with the database. No defaults.ALLOW_EMPTY_PASSWORD
: It can be used to allow blank passwords. Default: no
MYSQL_CLIENT_FLAVOR
: SQL database flavor. Valid values: mariadb
or mysql
. Default: mariadb.MYSQL_CLIENT_DATABASE_HOST
: Hostname for MariaDB server. Default: mariadb
MYSQL_CLIENT_DATABASE_PORT_NUMBER
: Port used by MariaDB server. Default: 3306
MYSQL_CLIENT_DATABASE_ROOT_USER
: Database admin user. Default: root
MYSQL_CLIENT_DATABASE_ROOT_PASSWORD
: Database password for the database admin user. No defaults.MYSQL_CLIENT_CREATE_DATABASE_NAME
: New database to be created by the mysql client module. No defaults.MYSQL_CLIENT_CREATE_DATABASE_USER
: New database user to be created by the mysql client module. No defaults.MYSQL_CLIENT_CREATE_DATABASE_PASSWORD
: Database password for the MYSQL_CLIENT_CREATE_DATABASE_USER
user. No defaults.MYSQL_CLIENT_CREATE_DATABASE_CHARACTER_SET
: Character set to use for the new database. No defaults.MYSQL_CLIENT_CREATE_DATABASE_COLLATE
: Database collation to use for the new database. No defaults.MYSQL_CLIENT_CREATE_DATABASE_PRIVILEGES
: Database privileges to grant for the user specified in MYSQL_CLIENT_CREATE_DATABASE_USER
to the database specified in MYSQL_CLIENT_CREATE_DATABASE_NAME
. No defaults.MYSQL_CLIENT_ENABLE_SSL_WRAPPER
: Whether to force SSL connections to the database via the mysql
CLI tool. Useful for applications that rely on the CLI instead of APIs. Default: no
MYSQL_CLIENT_ENABLE_SSL
: Whether to force SSL connections for the database. Default: no
MYSQL_CLIENT_SSL_CA_FILE
: Path to the SSL CA file for the new database. No defaultsMYSQL_CLIENT_SSL_CERT_FILE
: Path to the SSL CA file for the new database. No defaultsMYSQL_CLIENT_SSL_KEY_FILE
: Path to the SSL CA file for the new database. No defaultsALLOW_EMPTY_PASSWORD
: It can be used to allow blank passwords. Default: no
To configure OpenCart to send email using SMTP you can set the following environment variables:
OPENCART_SMTP_HOST
: SMTP host.OPENCART_SMTP_PORT
: SMTP port.OPENCART_SMTP_USER
: SMTP account user.OPENCART_SMTP_PASSWORD
: SMTP account password.PHP_ENABLE_OPCACHE
: Enable OPcache for PHP scripts. No default.PHP_EXPOSE_PHP
: Enables HTTP header with PHP version. No default.PHP_MAX_EXECUTION_TIME
: Maximum execution time for PHP scripts. No default.PHP_MAX_INPUT_TIME
: Maximum input time for PHP scripts. No default.PHP_MAX_INPUT_VARS
: Maximum amount of input variables for PHP scripts. No default.PHP_MEMORY_LIMIT
: Memory limit for PHP scripts. Default: 256M
PHP_POST_MAX_SIZE
: Maximum size for PHP POST requests. No default.PHP_UPLOAD_MAX_FILESIZE
: Maximum file size for PHP uploads. No default.This would be an example of SMTP configuration using a Gmail account:
docker-compose.yml
file present in this repository: opencart:
...
environment:
- OPENCART_DATABASE_USER=bn_opencart
- OPENCART_DATABASE_NAME=bitnami_opencart
- ALLOW_EMPTY_PASSWORD=yes
- OPENCART_SMTP_HOST=smtp.gmail.com
- OPENCART_SMTP_PORT=587
- [email protected]
- OPENCART_SMTP_PASSWORD=your_password
...
$ docker run -d --name opencart -p 80:8080 -p 443:8443 \
--env OPENCART_DATABASE_USER=bn_opencart \
--env OPENCART_DATABASE_NAME=bitnami_opencart \
--env OPENCART_SMTP_HOST=smtp.gmail.com \
--env OPENCART_SMTP_PORT=587 \
--env [email protected] \
--env OPENCART_SMTP_PASSWORD=your_password \
--network opencart-tier \
--volume /path/to/opencart-persistence:/bitnami \
bitnami/opencart:latest
The Bitnami OpenCart Docker image sends the container logs to stdout
. To view the logs:
$ docker logs opencart
Or using Docker Compose:
$ docker-compose logs opencart
You can configure the containers logging driver using the --log-driver
option if you wish to consume the container logs differently. In the default configuration docker uses the json-file
driver.
To backup your data, configuration and logs, follow these simple steps:
$ docker stop opencart
Or using Docker Compose:
$ docker-compose stop opencart
We need to mount two volumes in a container we will use to create the backup: a directory on your host to store the backup in, and the volumes from the container we just stopped so we can access the data.
$ docker run --rm -v /path/to/opencart-backups:/backups --volumes-from opencart busybox \
cp -a /bitnami/opencart /backups/latest
Restoring a backup is as simple as mounting the backup as volumes in the containers.
For the MariaDB database container:
$ docker run -d --name mariadb \
...
- --volume /path/to/mariadb-persistence:/bitnami/mariadb \
+ --volume /path/to/mariadb-backups/latest:/bitnami/mariadb \
bitnami/mariadb:latest
For the OpenCart container:
$ docker run -d --name opencart \
...
- --volume /path/to/opencart-persistence:/bitnami/opencart \
+ --volume /path/to/opencart-backups/latest:/bitnami/opencart \
bitnami/opencart:latest
Bitnami provides up-to-date versions of MariaDB and OpenCart, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. We will cover here the upgrade of the OpenCart container. For the MariaDB upgrade see: https://github.com/bitnami/bitnami-docker-mariadb/blob/master/README.md#upgrade-this-image
$ docker pull bitnami/opencart:latest
Stop the currently running container using the command
$ docker-compose stop opencart
Follow the steps in Backing up your container to take a snapshot of the current application state.
Remove the currently running container by executing the following command:
docker-compose rm -v opencart
Update the image tag in docker-compose.yml
and re-create your container with the new image:
$ docker-compose up -d
The Bitnami OpenCart Docker image is designed to be extended so it can be used as the base image for your custom web applications.
Before extending this image, please note there are certain configuration settings you can modify using the original image:
APACHE_HTTP_PORT_NUMBER
and APACHE_HTTPS_PORT_NUMBER
respectively.If your desired customizations cannot be covered using the methods mentioned above, extend the image. To do so, create your own image using a Dockerfile with the format below:
FROM bitnami/opencart
## Put your customizations below
...
Here is an example of extending the image with the following modifications:
vim
editorFROM bitnami/opencart
## Change user to perform privileged actions
USER 0
## Install 'vim'
RUN install_packages vim
## Revert to the original non-root user
USER 1001
## Enable mod_ratelimit module
RUN sed -i -r 's/#LoadModule ratelimit_module/LoadModule ratelimit_module/' /opt/bitnami/apache/conf/httpd.conf
## Modify the ports used by Apache by default
# It is also possible to change these environment variables at runtime
ENV APACHE_HTTP_PORT_NUMBER=8181
ENV APACHE_HTTPS_PORT_NUMBER=8143
EXPOSE 8181 8143
Based on the extended image, you can update the docker-compose.yml
file present in this repository to add other features:
opencart:
- image: bitnami/opencart:latest
+ build: .
ports:
- - '80:8080'
- - '443:8443'
+ - '80:8181'
+ - '443:8143'
environment:
+ - PHP_MEMORY_LIMIT=512m
...
root
user and the Apache daemon was started as the daemon
user. From now on, both the container and the Apache daemon run as user 1001
. You can revert this behavior by changing USER 1001
to USER root
in the Dockerfile, or user: root
in docker-compose.yml
. Consequences:
8080/8443
instead of 80/443
.To upgrade a deployment with the previous Bitnami OpenCart container image, which did not support non-root, the easiest way is to start the new image as a root user and updating the port numbers. Modify your docker-compose.yml
file as follows:
- ALLOW_EMPTY_PASSWORD=yes
+ user: root
ports:
- - '80:80'
- - '443:443'
+ - '80:8080'
+ - '443:8443'
volumes:
/bitnami/apache
) has been deprecated, and support for this feature will be dropped in the near future. Until then, the container will enable the Apache configuration from that volume if it exists. By default, and if the configuration volume does not exist, the configuration files will be regenerated each time the container is created. Users wanting to apply custom Apache configuration files are advised to mount a volume for the configuration at /opt/bitnami/apache/conf
, or mount specific configuration files individually./bitnami/php
) has been deprecated, and support for this feature will be dropped in the near future. Until then, the container will enable the PHP configuration from that volume if it exists. By default, and if the configuration volume does not exist, the configuration files will be regenerated each time the container is created. Users wanting to apply custom PHP configuration files are advised to mount a volume for the configuration at /opt/bitnami/php/conf
, or mount specific configuration files individually./opt/bitnami/apache/certs
has been deprecated, and support for this functionality will be dropped in the near future. Users wanting to enable custom certificates are advised to mount their certificate files on top of the preconfigured ones at /certs
.We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.
If you encountered a problem running this container, you can file an issue. Be sure to include the following information in your issue:
docker version
)docker info
Please, note this asset is a community-supported solution. This means that the Bitnami team is not actively working on new features/improvements nor providing support through GitHub Issues. Any new issue will stay open for 20 days to allow the community to contribute, after 15 days without activity the issue will be marked as stale being closed after 5 days.
The Bitnami team will review any PR that is created, feel free to create a PR if you find any issue or want to implement a new feature.
New versions and releases cadence are not going to be affected. Once a new version is released in the upstream project, the Bitnami container image will be updated to use the latest version, supporting the different branches supported by the upstream project as usual.
Copyright © 2022 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
http://www.apache.org/licenses/LICENSE-2.0
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.