Skip to content
Snippets Groups Projects
Select Git revision
  • c8c2e7fdcd92c5db9ae84d92bd9da2c8397abe5e
  • without_tipselection default
  • develop protected
  • fix/grafana-local-dashboard
  • wasp
  • fix/dashboard-explorer-freeze
  • master
  • feat/timerqueue
  • test/sync_debug_and_650
  • feat/sync_revamp_inv
  • wip/sync
  • tool/db-recovery
  • portcheck/fix
  • fix/synchronization
  • feat/new-dashboard-analysis
  • feat/refactored-analysis-dashboard
  • feat/new-analysis-dashboard
  • test/demo-prometheus-fpc
  • prometheus_metrics
  • wip/analysis-server
  • merge/fpc-test-value-transfer
  • v0.2.2
  • v0.2.1
  • v0.2.0
  • v0.1.3
  • v0.1.2
  • v0.1.1
  • v0.1.0
28 results

docker-network

user avatar
Luca Moser authored and GitHub committed
* normalize bind addresses prints

* refactors analysis plugins

* adds tests for parsing/serializing heartbeat packets

* adds additional test case

* normalize usage of word 'ids'

* updates packr files

* normalizes handler routes for static assets for the analysis web interface

* normalize config key names

* adjusts configs for new analysis config keys

* fixes review comments
6d3b2a2c
History

GoShimmer Network with Docker

Docker network

Running docker-compose spins up a GoShimmer network within Docker as schematically shown in the figure above. N defines the number of peer_replicas and can be specified when running the network. The peers can communicate freely within the Docker network while the autopeering network visualizer, master_peer's dashboard and web API are reachable from the host system on the respective ports.

The different containers (entry_node, peer_master, peer_replica) are based on the same config file and separate config file and modified as necessary, respectively.

How to use as development tool

Using a standalone throwaway Docker network can be really helpful as a development tool.

Prerequisites:

  • Docker 17.12.0+
  • Docker compose: file format 3.5

Reachable from the host system

It is therefore possible to send messages to the local network via the master_peer and observe log messages either via docker logs --follow CONTAINER or by starting the Docker network without the -d option, as follows.

docker-compose up --scale peer_replica=5

# remove containers and network
docker-compose down

Sometimes when changing files Docker does not detect the changes on a rebuild. Then the option --build needs to be used with docker-compose.