Public | Automated Build

Last pushed: 2 years ago
Short Description
Bitmessage GUI client with data persistence using X forwarding to render on host
Full Description


Bitmessage GUI in a Docker container


The purpose of this project is to make the Bitmessage GUI interface available on a system, through a Docker container, with the fluidity of applications natively installed.

A description of how and why this project came to be can be found at


git clone

cd docker-bitmessage-gui


The installation script will:

  • pull Docker image
  • make local directories
  • generate SSH keys
  • create symbolic links

Alternatively, you can execute the commands yourself:

#download Docker container image
docker pull j0rg3/bitmessage-gui

# make directory for Bitmessage configuration, data and SSH keys
# nothing will happen if directory already exists
mkdir -p ~/.config/PyBitmessage/keys

# generate keys for SSH
cd ~/.config/PyBitmessage/keys
ssh-keygen -b 4096 -P "" -C $"$(whoami)@$(hostname)-$(date -I)" -f docker-bitmessage-keys

# link so Docker container will see as pubkey
ln -fs authorized_keys

# link to Bitmessage script for system-wide access
ln -fs ~/docker-bitmessage-gui/bitmessage /usr/local/bin/bitmessage


The commands contained in the 'bitmessage' script:

DID=$(docker run -p 8444:8444 -v ~/.config/PyBitmessage/:/root/.config/PyBitmessage -v ~/.config/PyBitmessage/keys/:/root/.ssh/ -dit j0rg3/bitmessage-gui bash) && \
DIP=$(docker inspect $DID | grep IPAddress | cut -d '"' -f 4) && \ 
ssh -oStrictHostKeyChecking=no -oUserKnownHostsFile=/dev/null -oIdentityFile=~/.config/PyBitmessage/keys/docker-bitmessage-keys -X $DIP ./PyBitmessage/src/ && \
docker kill $DID


Docker Pull Command