pyth-crosschain/third_party/algorand/Dockerfile

# syntax=docker/dockerfile:1.2
FROM docker.io/algorand/stable:3.2.1@sha256:0a87978492680fd98e2cc410f59f2bfd7fef979f035eb060685d56a6e916b5bd

RUN mkdir -p /setup
ADD template.json /setup/

RUN ./goal network create -n sandnet -r /network -t /setup/template.json && echo rawr

RUN mkdir -p /network/Node/kmd-v0.5

ADD token /network/Node/algod.token
ADD token /network/Node/kmd-v0.5/kmd.token
ADD config.json /network/Node/config.json
ADD kmd_config.json /network/Node/kmd-v0.5/kmd_config.json

ENV ALGORAND_DATA=/network/Node
devnet: add algorand sandnet As far as I can tell, both primary and node are happy. We can't use https://github.com/algorand/sandbox since it makes too many assumptions about its environment (docker-compose, interactive development vs. reproducible CI usage). Instead, use the official mainnet Docker images and ship our own config. Caveat: "goal network create" is not reproducible and each Docker build will generate a new set of root keys. We can presumably avoid this by hardcoding the output of "goal network create" (using --noimportkeys to avoid having to vendor a SQLite DB.. we'd just re-import them to kmd at runtime, which is what goal is doing internally: https://github.com/algorand/go-algorand/blob/f51d2d7d5af1ef634bad99afeb1a910efe245177/netdeploy/networkTemplate.go#L131) Change-Id: I8c99c6150c9c244c9f12b68a58184c2d5697cee8 2021-12-08 16:32:16 -08:00			`# syntax=docker/dockerfile:1.2`
			`FROM docker.io/algorand/stable:3.2.1@sha256:0a87978492680fd98e2cc410f59f2bfd7fef979f035eb060685d56a6e916b5bd`

			`RUN mkdir -p /setup`
			`ADD template.json /setup/`

			`RUN ./goal network create -n sandnet -r /network -t /setup/template.json && echo rawr`

			`RUN mkdir -p /network/Node/kmd-v0.5`

			`ADD token /network/Node/algod.token`
			`ADD token /network/Node/kmd-v0.5/kmd.token`
			`ADD config.json /network/Node/config.json`
			`ADD kmd_config.json /network/Node/kmd-v0.5/kmd_config.json`

			`ENV ALGORAND_DATA=/network/Node`