# Bitwarden Workertools

Bitwarden Workertools is a Docker image containing the Bitwarden command-line tools for running Bitwarden tasks as an Octopus Deploy execution container. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/5517/bitwarden-workertools

## Description

Bitwarden Workertools is a Docker image containing the Bitwarden command-line tools for running Bitwarden tasks as an Octopus Deploy execution container.

## Platform availability

Available on 0 of 10 platforms.

## Health score

40/100 (Fair), based on 2 of 4 factors.
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Light to run: 60 (2 GB minimum RAM, runs on ARM)

## Links

- Docker Hub: https://hub.docker.com/r/octopuslabs/bitwarden-workertools

## Common questions

### Will Bitwarden tooling work if the bw CLI is missing from the execution container?

No. The tooling runs the Bitwarden CLI, and if bw is not installed the calls can fail with errors like spawn bw ENOENT, meaning the tool could not be found.

### What Bitwarden credential should be set so the tooling can access an account?

Set BW_SESSION to a real Bitwarden CLI session token. The server uses that token to sign in as you, and without it it cannot access your Bitwarden account.

### Can the tooling be pointed at a local build if the project was not built first?

No. Avoid the node dist/index.js setting unless you have already run the local build steps, because that file is only created by building from source.

### What domain should be used when generating certificates for a self-hosted Bitwarden domain?

Use the local domain you intend to use, such as bitwarden-host.lan, during certificate generation. The example accesses the instance over https on port 5880.

---
Source: Our Local Host (https://ourlocalhost.com/app/5517/bitwarden-workertools), the self-hosted and open-source app directory.
