orwa84/backdrop repository overview

⁠Introduction

This is a docker image of backdrop version 1.29.0 built using the "apache" Dockerfile variant, for both the arm64 and the amd64 architectures.

⁠Why

This image fixes some of the issue found in https://github.com/backdrop-ops/backdrop-docker⁠:

• Image cannot start⁠
• Docker compose does not work⁠
• Image not available for multiple architectures⁠

⁠GitHub repos

The repo for the official images which are outdated and not working (until my PR is merged): https://github.com/backdrop-ops/backdrop-docker⁠

The repo from which this image was built: https://github.com/diraneyya/backdrop-docker⁠

⁠Docker compose file

To try out backdrop locally, you can use the following docker compose configuration:

services:
  backdrop:
    image: orwa84/backdrop
    ports:
      - 8080:80
    environment:
      BACKDROP_DB_HOST: db
      BACKDROP_DB_USER: backdrop
      BACKDROP_DB_PASSWORD: backdrop

  db:
    image: mysql
    environment:
      MYSQL_USER: backdrop
      MYSQL_PASSWORD: backdrop
      MYSQL_ALLOW_EMPTY_PASSWORD: 'yes'
      MYSQL_DATABASE: backdrop

Store the above in a file named docker-compose.yml and run the command docker compose up from the same directory.

If the port 8080 is already taken and the above command fails, switch it to something else, such as 8088 or 8888.

If all goes well then you will be able to open the app in the browser either by using Docker Desktop, or by typing one of the following addresses into the address bar in your favourite browser: https://localhost:8080⁠, https://localhost:8088⁠, or https://localhost:8888⁠ (depending on which port you ended up using)

⁠Note about the compose config

The links feature used in the docker-compose config recommended as part of the official documentation does not work. Namely, the docker-compose config and the entrypoint.sh script seem both to be based on the assumption that if you link the db container to the app's container using the alias mysql, that the app would gain access the ENV variables of the MySQL container. Looking at the Docker Compose documentation, that is certainly NOT what links does. (Could it be that the author was confused between links and the legacy external_links feature?)