status-im
/
status-go
mirror of https://github.com/status-im/status-go.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
status-go/_assets/build/Dockerfile-bootnode

25 lines
729 B
Plaintext
Raw Permalink Normal View History

Upgrade Go to 1.13 in our Docker images (#1629)
2019-10-05 14:27:48 +00:00
FROM golang:1.13-alpine as builder
Custom status bootnodes (#968) This change makes invalidation mechanism more aggressive. With a primary goal to invalidate short living nodes faster. In current setup any node that became known in terms of discovery will stay in this state until it will fail to respond to 5 queries. Removing them earlier from a table allows to reduce latency for finding required nodes. The second change, one adds a version for discovery, separates status dht from ethereum dht. After we rolled out discovery it became obvious that our boot nodes became spammed with irrelevant nodes. And this made discovery process very long, for example with separate dht discovery takes ~2s, with mutual dht - it can take 1m-10m and there is still no guarantee to find a max amount of peers, cause status nodes is a very small part of whole ethereum infra. In my understanding, we don't need to be a part of ethereum dht, and lower latency is way more important for us. Closes: #941 Partially closes: #960 (960 requires futher investigations on devices)
2018-05-18 13:43:07 +00:00
Add labels to docker images and add Jenkinsfile to build docker images (#1160) * fixed generating `params.Version` * added labels to all Docker images including git_commit and the author of the build (using `$USER` env variable)
2018-08-24 10:25:07 +00:00
RUN apk add --no-cache make gcc musl-dev linux-headers git
Custom status bootnodes (#968) This change makes invalidation mechanism more aggressive. With a primary goal to invalidate short living nodes faster. In current setup any node that became known in terms of discovery will stay in this state until it will fail to respond to 5 queries. Removing them earlier from a table allows to reduce latency for finding required nodes. The second change, one adds a version for discovery, separates status dht from ethereum dht. After we rolled out discovery it became obvious that our boot nodes became spammed with irrelevant nodes. And this made discovery process very long, for example with separate dht discovery takes ~2s, with mutual dht - it can take 1m-10m and there is still no guarantee to find a max amount of peers, cause status nodes is a very small part of whole ethereum infra. In my understanding, we don't need to be a part of ethereum dht, and lower latency is way more important for us. Closes: #941 Partially closes: #960 (960 requires futher investigations on devices)
2018-05-18 13:43:07 +00:00
Add labels to docker images and add Jenkinsfile to build docker images (#1160) * fixed generating `params.Version` * added labels to all Docker images including git_commit and the author of the build (using `$USER` env variable)
2018-08-24 10:25:07 +00:00
ARG build_tags
ARG build_flags
Custom status bootnodes (#968) This change makes invalidation mechanism more aggressive. With a primary goal to invalidate short living nodes faster. In current setup any node that became known in terms of discovery will stay in this state until it will fail to respond to 5 queries. Removing them earlier from a table allows to reduce latency for finding required nodes. The second change, one adds a version for discovery, separates status dht from ethereum dht. After we rolled out discovery it became obvious that our boot nodes became spammed with irrelevant nodes. And this made discovery process very long, for example with separate dht discovery takes ~2s, with mutual dht - it can take 1m-10m and there is still no guarantee to find a max amount of peers, cause status nodes is a very small part of whole ethereum infra. In my understanding, we don't need to be a part of ethereum dht, and lower latency is way more important for us. Closes: #941 Partially closes: #960 (960 requires futher investigations on devices)
2018-05-18 13:43:07 +00:00
RUN mkdir -p /go/src/github.com/status-im/status-go
ADD . /go/src/github.com/status-im/status-go
Add labels to docker images and add Jenkinsfile to build docker images (#1160) * fixed generating `params.Version` * added labels to all Docker images including git_commit and the author of the build (using `$USER` env variable)
2018-08-24 10:25:07 +00:00
RUN cd /go/src/github.com/status-im/status-go && \
make bootnode \
BUILD_TAGS="$build_tags" \
BUILD_FLAGS="$build_flags"
Custom status bootnodes (#968) This change makes invalidation mechanism more aggressive. With a primary goal to invalidate short living nodes faster. In current setup any node that became known in terms of discovery will stay in this state until it will fail to respond to 5 queries. Removing them earlier from a table allows to reduce latency for finding required nodes. The second change, one adds a version for discovery, separates status dht from ethereum dht. After we rolled out discovery it became obvious that our boot nodes became spammed with irrelevant nodes. And this made discovery process very long, for example with separate dht discovery takes ~2s, with mutual dht - it can take 1m-10m and there is still no guarantee to find a max amount of peers, cause status nodes is a very small part of whole ethereum infra. In my understanding, we don't need to be a part of ethereum dht, and lower latency is way more important for us. Closes: #941 Partially closes: #960 (960 requires futher investigations on devices)
2018-05-18 13:43:07 +00:00
FROM alpine:latest
Add labels to docker images and add Jenkinsfile to build docker images (#1160) * fixed generating `params.Version` * added labels to all Docker images including git_commit and the author of the build (using `$USER` env variable)
2018-08-24 10:25:07 +00:00
LABEL maintainer="support@status.im"
LABEL source="https://github.com/status-im/status-go"
LABEL description="bootnode is an Ethereum bootnode with patched Discovery V5."
Custom status bootnodes (#968) This change makes invalidation mechanism more aggressive. With a primary goal to invalidate short living nodes faster. In current setup any node that became known in terms of discovery will stay in this state until it will fail to respond to 5 queries. Removing them earlier from a table allows to reduce latency for finding required nodes. The second change, one adds a version for discovery, separates status dht from ethereum dht. After we rolled out discovery it became obvious that our boot nodes became spammed with irrelevant nodes. And this made discovery process very long, for example with separate dht discovery takes ~2s, with mutual dht - it can take 1m-10m and there is still no guarantee to find a max amount of peers, cause status nodes is a very small part of whole ethereum infra. In my understanding, we don't need to be a part of ethereum dht, and lower latency is way more important for us. Closes: #941 Partially closes: #960 (960 requires futher investigations on devices)
2018-05-18 13:43:07 +00:00
RUN apk add --no-cache ca-certificates bash
COPY --from=builder /go/src/github.com/status-im/status-go/build/bin/bootnode /usr/local/bin/
fix entrypoint for bootnode Docker image Signed-off-by: Jakub Sokołowski <jakub@status.im>
2019-12-16 22:27:13 +00:00
ENTRYPOINT ["/usr/local/bin/bootnode"]