cascade/ipfs-cluster
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
7b499263af
ipfs-cluster/Dockerfile-test

65 lines
2.0 KiB
Plaintext
Raw Normal View History

Bump things to Go 1.13
2019-10-04 17:27:02 +00:00
FROM golang:1.13-stretch AS builder
Docker test image build (#103) * First draft of test dockerfile build * Test dockerfile, build works, container runs and cluster tests go through * Removed fifo for output * renaming dockerfile
2017-06-16 13:07:08 +00:00
MAINTAINER Hector Sanjuan <hector@protocol.ai>
Dockerfile-test: Add bash to busybox Remove the debian-stretch Dockerfile-test and put the busybox one with bash in its place. Tested that kubernetes-ipfs runs with it. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-10-21 09:52:25 +00:00
# This build state just builds the cluster binaries
Fix #154: Update Dockerfiles After changes on how the final docker image for go-ipfs is generated, our Dockerfiles failed to build. The new version is inspired on go-ipfs Dockerfile. It takes advantage of docker >= v17.06 which allows multi-stage Dockerfiles with several FROM directives and COPY --from. This allows build freely on a first stage, without thinking of cleaning up, and then just copy the final artifacts to a second, minimal image. The Dockerfile-test is similarly updated. Minor changes have been applied to the entrypoints. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-10-20 10:13:49 +00:00
ENV GOPATH /go
ENV SRC_PATH $GOPATH/src/github.com/ipfs/ipfs-cluster
Enable go.mod for ipfs-cluster
2019-03-08 01:44:07 +00:00
ENV GO111MODULE on
Dockerfiles: enable goproxy This should improve the amount of CI errors lately when hitting github.
2019-08-07 09:22:46 +00:00
ENV GOPROXY=https://proxy.golang.org
Fix #154: Update Dockerfiles After changes on how the final docker image for go-ipfs is generated, our Dockerfiles failed to build. The new version is inspired on go-ipfs Dockerfile. It takes advantage of docker >= v17.06 which allows multi-stage Dockerfiles with several FROM directives and COPY --from. This allows build freely on a first stage, without thinking of cleaning up, and then just copy the final artifacts to a second, minimal image. The Dockerfile-test is similarly updated. Minor changes have been applied to the entrypoints. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-10-20 10:13:49 +00:00
COPY . $SRC_PATH
WORKDIR $SRC_PATH
RUN make install
Dockerfile-test: Add bash to busybox Remove the debian-stretch Dockerfile-test and put the busybox one with bash in its place. Tested that kubernetes-ipfs runs with it. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-10-21 09:52:25 +00:00
RUN cd /tmp && \
wget https://github.com/stedolan/jq/releases/download/jq-1.5/jq-linux64 && \
chmod +x jq-linux64
Fix #154: Update Dockerfiles After changes on how the final docker image for go-ipfs is generated, our Dockerfiles failed to build. The new version is inspired on go-ipfs Dockerfile. It takes advantage of docker >= v17.06 which allows multi-stage Dockerfiles with several FROM directives and COPY --from. This allows build freely on a first stage, without thinking of cleaning up, and then just copy the final artifacts to a second, minimal image. The Dockerfile-test is similarly updated. Minor changes have been applied to the entrypoints. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-10-20 10:13:49 +00:00
#------------------------------------------------------
Dockerfile-test: use go-ipfs:master Allows us to test against latest ipfs (either it's broken and this helps finding out, or it's not broken anymore and we don't lose time trying to figure out why). License: MIT Signed-off-by: Hector Sanjuan <code@hector.link>
2017-11-23 11:09:13 +00:00
FROM ipfs/go-ipfs:master
Fix #154: Update Dockerfiles After changes on how the final docker image for go-ipfs is generated, our Dockerfiles failed to build. The new version is inspired on go-ipfs Dockerfile. It takes advantage of docker >= v17.06 which allows multi-stage Dockerfiles with several FROM directives and COPY --from. This allows build freely on a first stage, without thinking of cleaning up, and then just copy the final artifacts to a second, minimal image. The Dockerfile-test is similarly updated. Minor changes have been applied to the entrypoints. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-10-20 10:13:49 +00:00
MAINTAINER Hector Sanjuan <hector@protocol.ai>
Dockerfile-test: Add bash to busybox Remove the debian-stretch Dockerfile-test and put the busybox one with bash in its place. Tested that kubernetes-ipfs runs with it. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-10-21 09:52:25 +00:00
# This is the container which just puts the previously
# built binaries on the go-ipfs-container.
Docker test image build (#103) * First draft of test dockerfile build * Test dockerfile, build works, container runs and cluster tests go through * Removed fifo for output * renaming dockerfile
2017-06-16 13:07:08 +00:00
ENV GOPATH /go
ENV SRC_PATH /go/src/github.com/ipfs/ipfs-cluster
ENV IPFS_CLUSTER_PATH /data/ipfs-cluster
Docker: improve for CRDTs This: * Allows choosing the consensus for the automatic "init" on Docker with IPFS_CLUSTER_CONSENSUS. * Removes IPFS_PATH and the sed replacements for 0.0.0.0 on RestAPI and Ipfsproxy endpoints because these are easily supported by setting env vars correctly and pose some security risk when running with net=host. * Brings up to date Dockerfile-test and Dockerfile-bundle, even if mostly unused.
2019-08-13 12:43:07 +00:00
ENV IPFS_CLUSTER_CONSENSUS crdt
ENV IPFS_CLUSTER_RESTAPI_HTTPLISTENMULTIADDRESS /ip4/0.0.0.0/tcp/9094
ENV IPFS_CLUSTER_IPFSPROXY_LISTENMULTIADDRESS /ip4/0.0.0.0/tcp/9095
Docker test image build (#103) * First draft of test dockerfile build * Test dockerfile, build works, container runs and cluster tests go through * Removed fifo for output * renaming dockerfile
2017-06-16 13:07:08 +00:00
Fix #154: Update Dockerfiles After changes on how the final docker image for go-ipfs is generated, our Dockerfiles failed to build. The new version is inspired on go-ipfs Dockerfile. It takes advantage of docker >= v17.06 which allows multi-stage Dockerfiles with several FROM directives and COPY --from. This allows build freely on a first stage, without thinking of cleaning up, and then just copy the final artifacts to a second, minimal image. The Dockerfile-test is similarly updated. Minor changes have been applied to the entrypoints. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-10-20 10:13:49 +00:00
EXPOSE 9094
EXPOSE 9095
EXPOSE 9096
Docker test image build (#103) * First draft of test dockerfile build * Test dockerfile, build works, container runs and cluster tests go through * Removed fifo for output * renaming dockerfile
2017-06-16 13:07:08 +00:00
Dockerfile-test: Add bash to busybox Remove the debian-stretch Dockerfile-test and put the busybox one with bash in its place. Tested that kubernetes-ipfs runs with it. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-10-21 09:52:25 +00:00
COPY --from=builder $GOPATH/bin/ipfs-cluster-service /usr/local/bin/ipfs-cluster-service
COPY --from=builder $GOPATH/bin/ipfs-cluster-ctl /usr/local/bin/ipfs-cluster-ctl
Docker: improve for CRDTs This: * Allows choosing the consensus for the automatic "init" on Docker with IPFS_CLUSTER_CONSENSUS. * Removes IPFS_PATH and the sed replacements for 0.0.0.0 on RestAPI and Ipfsproxy endpoints because these are easily supported by setting env vars correctly and pose some security risk when running with net=host. * Brings up to date Dockerfile-test and Dockerfile-bundle, even if mostly unused.
2019-08-13 12:43:07 +00:00
COPY --from=builder $SRC_PATH/docker/test-entrypoint.sh /usr/local/bin/test-entrypoint.sh
Fix #154: Update Dockerfiles After changes on how the final docker image for go-ipfs is generated, our Dockerfiles failed to build. The new version is inspired on go-ipfs Dockerfile. It takes advantage of docker >= v17.06 which allows multi-stage Dockerfiles with several FROM directives and COPY --from. This allows build freely on a first stage, without thinking of cleaning up, and then just copy the final artifacts to a second, minimal image. The Dockerfile-test is similarly updated. Minor changes have been applied to the entrypoints. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-10-20 10:13:49 +00:00
COPY --from=builder $SRC_PATH/docker/random-stopper.sh /usr/local/bin/random-stopper.sh
COPY --from=builder $SRC_PATH/docker/random-killer.sh /usr/local/bin/random-killer.sh
COPY --from=builder $SRC_PATH/docker/wait-killer-stopper.sh /usr/local/bin/wait-killer-stopper.sh
COPY --from=builder $SRC_PATH/docker/cluster-restart.sh /usr/local/bin/cluster-restart.sh
Docker test image build (#103) * First draft of test dockerfile build * Test dockerfile, build works, container runs and cluster tests go through * Removed fifo for output * renaming dockerfile
2017-06-16 13:07:08 +00:00
Dockerfile-test: Add bash to busybox Remove the debian-stretch Dockerfile-test and put the busybox one with bash in its place. Tested that kubernetes-ipfs runs with it. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-10-21 09:52:25 +00:00
# Add jq
COPY --from=builder /tmp/jq-linux64 /usr/local/bin/jq
# Add bash
COPY --from=builder /bin/bash /bin/bash
COPY --from=builder /lib/x86_64-linux-gnu/libtinfo.so.5 /lib64/libtinfo.so.5
Switch to root user to create data directory License: MIT Signed-off-by: Kishan Mohanbhai Sagathiya <kishansagathiya@gmail.com>
2018-12-13 10:33:22 +00:00
USER root
Use plain debian for Dockerfile-test License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-10-20 22:12:08 +00:00
Dockerfile-test: Add bash to busybox Remove the debian-stretch Dockerfile-test and put the busybox one with bash in its place. Tested that kubernetes-ipfs runs with it. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-10-21 09:52:25 +00:00
RUN mkdir -p $IPFS_CLUSTER_PATH && \
chown 1000:100 $IPFS_CLUSTER_PATH
Put a note for deprecating json fields Put a note for deprecating json fields that they are only here to maintain compatibility and they will be removed in future Start using env vars starting with `CLUSTER_IPFSPROXY` License: MIT Signed-off-by: Kishan Mohanbhai Sagathiya <kishansagathiya@gmail.com>
2018-12-17 02:54:17 +00:00
USER ipfs
Dockerfile-test: Add bash to busybox Remove the debian-stretch Dockerfile-test and put the busybox one with bash in its place. Tested that kubernetes-ipfs runs with it. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-10-21 09:52:25 +00:00
VOLUME $IPFS_CLUSTER_PATH
Docker: improve for CRDTs This: * Allows choosing the consensus for the automatic "init" on Docker with IPFS_CLUSTER_CONSENSUS. * Removes IPFS_PATH and the sed replacements for 0.0.0.0 on RestAPI and Ipfsproxy endpoints because these are easily supported by setting env vars correctly and pose some security risk when running with net=host. * Brings up to date Dockerfile-test and Dockerfile-bundle, even if mostly unused.
2019-08-13 12:43:07 +00:00
ENTRYPOINT ["/usr/local/bin/test-entrypoint.sh"]
Dockerfile-test: Add bash to busybox Remove the debian-stretch Dockerfile-test and put the busybox one with bash in its place. Tested that kubernetes-ipfs runs with it. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-10-21 09:52:25 +00:00
Fix #216: Docker does not like an env variable in CMD (anymore?) This used to work. Even if it's been surfaced by 4a8759939 we were extensively testing the Dockerfile before that release. License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
2017-10-31 10:46:32 +00:00
# Defaults would go here
Service: Select consensus on "init" (not on "daemon") Fixes #865. This makes the necessary changes so that consensu is selected on "init" with a flag set, by default, to "crdt". This generates only a "crdt" or a "raft" section, not both. If the configuration file has a "raft" section, "raft" will be used to start the daemon. If it has a "crdt" section, "crdt" will be used. If it has none or both sections, an error will happen. This also affects "state *" commands, which will now autoselect how to work from the existing configuration.
2019-08-09 14:00:55 +00:00
CMD ["daemon"]
Reference in New Issue Copy Permalink