openvk/install/automated/docker
Alexander Minkin d441f928f1
fix(docker): set openvk dir as workdir
So that opening a shell with `docker compose exec openvk bash` would lead to openvk dir instead of ~/html which is not used
2024-11-03 16:39:01 +03:00
..
acl_handler.sh fix(containers): 🔊 Set log output to stdout 2023-10-03 01:49:53 +03:00
base-php-apache.Dockerfile ci(docker): bump PHP version to 8.2 2023-12-10 21:21:50 +03:00
base-php-cli.Dockerfile ci(docker): bump PHP version to 8.2 2023-12-10 21:21:50 +03:00
chandler.example.yml feat(docker): provide example config 2023-12-10 22:23:22 +03:00
docker-compose.dev.yml build: add additional compose file for devs 2024-11-03 16:38:59 +03:00
docker-compose.yml build(docker): remove version from compose file and add name 2024-11-03 16:39:00 +03:00
mariadb-eventdb.Dockerfile CI for OpenVK, Kubernetes and Docker deployments (#735) 2022-10-30 14:44:14 +03:00
mariadb-primary.Dockerfile CI for OpenVK, Kubernetes and Docker deployments (#735) 2022-10-30 14:44:14 +03:00
openvk.Dockerfile fix(docker): set openvk dir as workdir 2024-11-03 16:39:01 +03:00
openvk.example.yml fix: remove fartscroll 2024-09-07 18:29:44 +03:00
Readme.md build: add additional compose file for devs 2024-11-03 16:38:59 +03:00

Docker

Note: If you want to build images for multiple architectures, you must use buildx. See Docker Buildx for more information.

If unsure, skip to single-arch image build instructions.

Build

Note: commands below must be run from the this directory (/install/automated/docker/).

Multi-arch (arm64, amd64)

Base images:

docker buildx build --platform linux/amd64,linux/arm64 -t ghcr.io/openvk/openvk/php:8.2-cli ../../.. --load -f base-php-cli.Dockerfile
docker buildx build --platform linux/amd64,linux/arm64 -t ghcr.io/openvk/openvk/php:8.2-apache ../../.. --load -f base-php-apache.Dockerfile

DB images:

docker buildx build --platform linux/amd64,linux/arm64 -t ghcr.io/openvk/openvk/mariadb:10.9-primary ../../.. --load -f mariadb-primary.Dockerfile
docker buildx build --platform linux/amd64,linux/arm64 -t ghcr.io/openvk/openvk/mariadb:10.9-eventdb ../../.. --load -f mariadb-eventdb.Dockerfile

OpenVK main image:

docker buildx build --platform linux/amd64,linux/arm64 -t ghcr.io/openvk/openvk/openvk:latest ../../.. --load -f openvk.Dockerfile

Single-arch

Base images:

docker build -t ghcr.io/openvk/openvk/php:8.2-cli ../../.. -f base-php-cli.Dockerfile
docker build -t ghcr.io/openvk/openvk/php:8.2-apache ../../.. -f base-php-apache.Dockerfile

DB images:

docker build -t ghcr.io/openvk/openvk/mariadb:10.9-primary ../../.. -f mariadb-primary.Dockerfile
docker build -t ghcr.io/openvk/openvk/mariadb:10.9-eventdb ../../.. --f mariadb-eventdb.Dockerfile

OpenVK main image:

docker build -t ghcr.io/openvk/openvk/openvk:latest ../../.. -f openvk.Dockerfile

Run

If you have Docker Desktop installed, then you should have docker compose installed automatically. If not, refer to Docker Compose for installation instructions.

Example configurations are located in this directory for convenience. Before start, copy openvk.example.yml to openvk.yml, then chandler.example.yml to chandler.yml and edit them to your liking.

Start is simple as docker compose up -d. You can also use docker compose up to see logs.

  • OpenVK will be available at http://localhost:8080/.
  • PHPMyAdmin will be available at http://localhost:8081/.
  • Adminer will be available at http://localhost:8082/.

Running in development environment

By using additional docker-compose.dev.yml file you can develop OpenVK in Docker with automatic updates as you edit and save your code. Simply run:

docker compose -f docker-compose.yml -f docker-compose.dev.yml up --watch