Skip to content

README.md

Latest commit

 

History

History
43 lines (36 loc) · 1.92 KB

README.md

File metadata and controls

43 lines (36 loc) · 1.92 KB

Notes

  • This configuration is intended for WSL2.
  • This configuration sets the container's non-root user to match the user on the host.
  • Docker Desktop does not support bind propagation, so this setting does not mount path for browsing mounted snapshot.
  • You can adjust bind mount and .env file if:
    • you are not using local or network-attached repository.
    • you need to add or remove backup locations.

Instruction

Before running Kopia repository server, you should create TLS certificate and key. If you have a certificate from CA, you can pass this step and move cert and key to ${VAULT_PATH}/${REPO_NAME}.cert and ${VAULT_PATH}/${REPO_NAME}.key (See below for env meaning).

sudo ./create_tls_cert.sh

You should duplicate .env.sample and rename the copy to .env. Then, adjust the .env file to fit your configuration.

  • TZ: Time Zone
  • USER_ID, GROUP_ID, USER_NAME, GROUP_NAME: Non-root user and group that exist in host
  • KOPIA_PASSWORD: Kopia respository password
  • KOPIA_SERVER_CONTROL_PASSWORD: Password for the user primarily managing KopiaUI
  • VAULT_PATH: Path of a directory that has cert and key files in it
  • REPO_NAME: Used to name cert and key files

The empty directories cache, config, and logs should be created in the same directory as compose.yaml. If you skip this step, Docker Compose will create the directories with root ownership, which can prevent non-root users in the container from writing to the bind mounts.

To run Kopia repository server:

docker compose up

To create Kopia filesystem repository:

docker exec -it Kopia kopia create filesystem --path /repository

To connect to Kopia filesystem repository:

docker exec -it Kopia kopia repository connect filesystem --path /repository

To add user accounts:

docker exec -it Kopia kopia server user add myuser@mylaptop