wireapp / wireapp/wire-server-deploy

Question: Local testing setup

Open
#332 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
113
Forks
44
PR merge metrics
No merged PRs in 30d

Description

Today I was trying to build and run wire-server on my local machine.
I walked through this guide: https://docs.wire.com/how-to/install/kubernetes.html
Option 2 was my choice. I created a "target" container for deployment with root password-less SSH-access.

It looks that the guide assumes the single target machine. But I couldn't pass this step (ran from inside of the docker container with all dependencies):

poetry run ansible-playbook -i hosts.ini kubernetes.yml -vv

The "target" container is debian-slim (I tried alpine as well, but apparently it is not supported).
The SSH-access is not a problem, I verified it. The errors are weird and change sometime.
Either lock of dpkg, or complaining that it is impossible to gain root privileges (with root SSH-login!).

It feels for me like simultaneous Ansible jobs are conflicting with each other.
Is single-node deployment really supported?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Kubernetes installation guide, especially Option 2, and reproduce poetry run ansible-playbook -i hosts.ini kubernetes.yml -vv against the described single target container. Capture the exact dpkg and privilege errors and determine whether single-node deployment is supported; done means the support status and required setup are clearly documented or the failure is reproducible and actionable.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, kubernetes
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.