9b55169251
* Update Dockerfile
Since parity is built for "mission critical use", I thought other operators may see the need for this.
Adding the `curl` and `jq` commands allows for an extremely simple health check to be usable in container orchestrators.
For example. Here is a health check for a parity docker container running in Kubernetes.
This can be setup as a readiness Probe that would prevent clustered nodes that aren't ready from serving traffic.
```bash
#!/bin/bash
ETH_SYNCING=$(curl -X POST --data '{"jsonrpc":"2.0","method":"eth_syncing","params":[],"id":1}' http://localhost:8545 -H 'Content-Type: application/json')
RESULT=$(echo "$ETH_SYNCING | jq -r .result)
if [ "$RESULT" == "false" ]; then
echo "Parity is ready to start accepting traffic"
exit 0
else
echo "Parity is still syncing the blockchain"
exit 1
fi
```
* add sync check script
39 lines
940 B
Docker
39 lines
940 B
Docker
FROM ubuntu:xenial
|
|
MAINTAINER Parity Technologies <devops@parity.io>
|
|
#set ENVIROMENT
|
|
ARG TARGET
|
|
ENV TARGET ${TARGET}
|
|
|
|
# install tools and dependencies
|
|
RUN apt update && apt install -y --no-install-recommends openssl libudev-dev file curl jq
|
|
|
|
# show backtraces
|
|
ENV RUST_BACKTRACE 1
|
|
|
|
#cleanup Docker image
|
|
RUN apt autoremove -y
|
|
RUN apt clean -y
|
|
RUN rm -rf /tmp/* /var/tmp/* /var/lib/apt/lists/*
|
|
|
|
RUN groupadd -g 1000 parity \
|
|
&& useradd -m -u 1000 -g parity -s /bin/sh parity
|
|
|
|
USER parity
|
|
|
|
WORKDIR /home/parity
|
|
|
|
ENV PATH "~/bin:${PATH}"
|
|
|
|
#add TARGET to docker image
|
|
COPY artifacts/x86_64-unknown-linux-gnu/$TARGET ./bin/$TARGET
|
|
|
|
# Build a shell script because the ENTRYPOINT command doesn't like using ENV
|
|
RUN echo "#!/bin/bash \n ${TARGET} \$@" > ./entrypoint.sh
|
|
RUN chmod +x ./entrypoint.sh
|
|
|
|
ADD check_sync.sh /check_sync.sh
|
|
|
|
# setup ENTRYPOINT
|
|
EXPOSE 5001 8080 8082 8083 8545 8546 8180 30303/tcp 30303/udp
|
|
ENTRYPOINT ["./entrypoint.sh"]
|