The current version of parity/parity:*
execute the parity binary as the parity
user, creating issues such as
Error upgrading parity data: CannotCreateConfigPath
when mounting in ContainerOS.
Due to the instability of the Parity CI/CD pipeline for docker images, we also built our own which is triggered when Parity pushes an update to https://hub.docker.com/r/parity/parity.
Our Docker Hub repository is linked to the parity/parity:*
one. The link is only for notification purposes. The image is rebuilt from scratch using rust:slim. (We are still testing if automatic rebuilds work as expected)
It uses exactly the same tags as parity/parity, but we also added a new tag kryha/parity:secretstore
which builds on beta releases with the Secret Store feature enabled.
All images are multi-stage docker builds and the final ones are slim based on ubuntu:latest
(which is LTS).
This is an update that also allows it to run without modifications in docker-compose on ContainerOS and Kubernetes environments because the binary is executed as root within the container.
Please make sure that you are using the correct paths.
Docker Hub repository: https://hub.docker.com/r/kryha/parity
Docker-compose example:
parity:
image: kryha/parity:beta
volumes:
- .parity/:/root/parity/
command:
- --chain=tobalaba
- --jsonrpc-apis=all
- --jsonrpc-interface=all
- --jsonrpc-cors=all
- --ws-port=8546
- --ws-interface=all
- --ws-origins=all
- --ws-hosts=all
Example live deployment: https://ewf.kryha.io