Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums

Content

Support Installation & Updates
  1. OpenProject
  2. Forums
  3. Support Installation & Updates
  4. Docker Compose: Customization networks / multiple Instances

Docker Compose: Customization networks / multiple Instances

Added by Marco Morath 25 days ago

I have installed an instance with version 15 as a Docker container with Docer Compose. When the container is started, three networks are created (frontend, backend, default). While frontend and backend have the typical network ranges (172.x.x.x), default apparently has a different range (192.168.16.x). This results in me having overlapping networks as I already have the 192.168.16.x network elsewhere.
Is it possible to change the default network to the usual Docker range as well (172.x.x.x) so that there is no overlap?

There is also another problem. I need to install a second instance on the same host. However, it seems that the containers are then overwritten because they seem to have the same name. In any case, I can't manage to run two instances in parallel. How can I manage this?


Replies (1)

RE: Docker Compose: Customization networks / multiple Instances - Added by Marco Morath 20 days ago

I have solved the two problems in the meantime.

With regard to network segmentation, it is possible to determine manually defined address ranges by adding the desired ranges to the Networks section and also adding the default network to prevent automatic generation in the background:

networks:
  frontend:
    driver: bridge
    name: openproject_app_1_frontend
    ipam:
      config:
        -subnet: 172.1.1.0/24
  backend:
    driver: bridge
    name: openproject_app_1_backend
    ipam:
      config:
        -subnet: 172.1.2.0/24
  default:
    driver: bridge
    name: openproject_app_1_default
    ipam:
      config:
        -subnet: 172.1.3.0/24

The address range 172.2.x.0/24 is then used in the second app.


I had another error with the problem with the two instances running in parallel.
If you clone the Git repository of OpenProject, the main folder “openproject” is also cloned. This folder is used for the name of the stack on the system. It must therefore be renamed for multiple instances.

/opt/openproject_app_1/...
/opt/openproject_app_2/...

The app files (docker-compose.yml etc) must then be located directly within the app folders (no further subfolders in between).

  • (1 - 1/1)
Loading...