You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 2, 2021. It is now read-only.
I'm trying to modify the image so that it excludes SELF as a peer. For example, node1 should only connect to node2 and node3, node2 should only connect to node1 and node3, and node3 should only connect to node1 and node2.
I've modified example/local.env by making three separate PREFERRED_PEERS lists. Here it is partially:
However, when I build and run the docker images and look in /etc/confd (and also /stellar-core.cfg,) it seems like my changes aren't registered. /etc/confd contains the original stellar-core.cfg.tmpl before my modifications.
Here is how I'm building and subsequently running the container:
docker build -t cell:1 --no-cache .
#delete the images first
sudo docker rm -f db1 || true
sudo docker rm -f db2 || true
sudo docker rm -f db3 || true
sudo docker rm -f node1 || true
sudo docker rm -f node2 || true
sudo docker rm -f node3 || true
for N in 1 2; do
# We need to map the ports
peerport=$(($N+1))
echo "$peerport"
sudo docker run --rm --name db$N -p 544$N:5432 --env-file examples/local.env -d stellar/stellar-core-state
sudo docker run --rm --name node$N --volumes-from db$N --env-file examples/local.env -p 116${peerport}5:116${peerport}5 -d stellar/stellar-core /start node$N fresh forcescp
done
for N in 3; do
peerport=$(($N+1))
sudo docker run --rm --name db$N -p 544$N:5432 --env-file examples/local.env -d stellar/stellar-core-state
sudo docker run --rm --name node$N -p 116${peerport}5:116${peerport}5 --volumes-from db$N --env-file examples/local.env -d stellar/stellar-core /start node$N fresh
done
How do I get this docker image to recognize my changes to the stellar-core template, and build a new stellar-core.cfg accordingly?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm trying to modify the image so that it excludes
SELF
as a peer. For example, node1 should only connect to node2 and node3, node2 should only connect to node1 and node3, and node3 should only connect to node1 and node2.I've modified
example/local.env
by making three separatePREFERRED_PEERS
lists. Here it is partially:Next, in
confd
, I modifiedtemplates/stellar-core.cfg.tmpl
like this:However, when I build and run the docker images and look in
/etc/confd
(and also/stellar-core.cfg
,) it seems like my changes aren't registered./etc/confd
contains the originalstellar-core.cfg.tmpl
before my modifications.Here is how I'm building and subsequently running the container:
How do I get this docker image to recognize my changes to the stellar-core template, and build a new stellar-core.cfg accordingly?
The text was updated successfully, but these errors were encountered: