Explanation

Docker Swarm is a container orchestration mode for Docker that allows you to deploy and manage multi-container applications across one or more Docker hosts. Instead of starting containers manually with ##docker run## or locally with Docker Compose, Docker Swarm uses stack definitions to deploy services in a managed cluster environment. XWiki can be deployed with Docker Swarm by using the XWiki Docker images together with a stack file. 

Docker Swarm also provides additional features that are useful in production environments, including:

• Docker secrets for sensitive values such as database usernames and passwords.
• Docker configs for external configuration files.

When you deploy XWiki with Docker Swarm, Docker can automatically:

• create overlay networks for the services
• run the XWiki and database services
• manage persistent volumes
• restart failed services
• scale services when needed

A typical XWiki Swarm deployment includes:

• one XWiki service
• one database service (for example MySQL)
• persistent volumes for application and database data
• secrets for database credentials

With Docker Swarm, XWiki can be deployed using stack files, such as:

• Run XWiki (MySQL on Tomcat) Using Docker Swarm
• Run XWiki (MariaDB on Tomcat) Using Docker Swarm
• Run XWiki (PostgreSQL on Tomcat) Using Docker Swarm

FAQ

Why is persistent storage needed for XWiki Docker installation?

Persistent storage is required to ensure that XWiki data is not lost when the container is stopped, restarted, or upgraded. To enable persistent storage, XWiki must be configured to store its data outside the container filesystem.

More

To find more about the current topic, you can search or use the table below and filter the columns to narrow your choices.