Data3.Network Documentation
  • Introduction to Data3
  • Data3 Concepts
    • Accounts
    • Address
    • Nodes
    • Types of Nodes
    • Node Providers
    • Database Deployment
    • Console
    • Use Case
  • Getting Started
    • Data3 Console
      • Signup on Data3 Console
      • Wallets
    • For Customers
      • Quick Start Guide
      • Signup on Data3 Console
      • Request Databases
      • Manage Your Databases
      • Use Your Databases
    • For Node Providers
      • Quick Start Guide
      • Signup at Data3 Console
      • Bid For Customer Requests
    • For Developers
      • Signup
      • Open Source
      • Contribute
  • For Customers
    • Access
    • Application Configuration
    • Database Configuration
    • Data Migration
    • Security
      • Users
      • Keys
    • Observability
  • For Node Providers
    • Node Provider Service
      • What is the Node Provider Service?
      • Node Provider Service Architecture
      • Node Provider Onetime Setup
        • Prerequisites
        • Docker data3-node-provider
        • Configure
        • Deploy data3-node-provider
        • Validate
        • Troubleshoot
    • Data3 Storage Node
      • What is the Data3 Storage Node?
      • Storage Node Architecture
      • Storage Node Setup
        • Prerequisites
        • Docker data3-storage-node
        • Configure
        • Deploy data3-storage-node
        • Validate
        • Troubleshoot
    • External Pricing Engine
    • External Deployment Engine
    • Node Tokenomics
      • Staking
      • Customer Payments
      • Incentivization
      • Pricing
    • Nodes
      • Validator Node
      • Audit Node
      • Storage Node
    • Console
  • Product
    • Roadmap
    • Releases
    • Updates
  • Data3 Solutions
    • DApps
    • Web3 Social
    • Web3 Gaming
    • Web3 Exchanges
    • Artificial Intelligence
    • SaaS Applications
    • IoT
    • Dev Database
  • Tokenomics
    • Best Practices
    • Bid for Database Requests
  • Governance & Policies
    • Governance Framework
    • Node Provider Policies
    • Data Handling Policies
    • Security Policies
    • Privacy Policies
    • For Developers
      • Architecture
      • API
      • SDKs and Libraries
      • Protocols & Algorithms
  • Community
  • FAQs
  • Legal
Powered by GitBook
On this page
  • TL;DR
  • Getting Started
  • Get this image
  • Launch data3-storage-node
  • Using a Docker Compose file
  1. For Node Providers
  2. Data3 Storage Node
  3. Storage Node Setup

Docker data3-storage-node

PreviousPrerequisitesNextConfigure

Last updated 1 year ago

See detailed instructions at

TL;DR

docker run --name storage-node-1 kandolanetwork/data3-storage-node:latest

Getting Started

Get this image

The recommended way to get the data3-storage-node Docker Image is to pull the prebuilt image from the .

docker pull kandolanetwork/data3-storage-node:latest

To use a specific version, you can pull a versioned tag. You can view the in the Docker Hub Registry.

docker pull kandolanetwork/data3-storage-node:[TAG]

Launch data3-storage-node

Step 1: Create a network

docker network create data3-storage-node-network --driver bridge

Step 2: Create data volumes

docker volume create data3-storage-node-volume

Step 3: Launch the Data3 Storage Node instance

docker run -d --name node-provider-1 \
    --network data3-storage-node-network \
    --volume data3-storage-node-volume
    kandolanetwork/data3-storage-node:latest

See below for environment variables that you can pass using -e docker run flag.

Using a Docker Compose file

When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new bridge network named data3-storage-node-network.

version: '2.24.5'
services:
  data3-storage-node:
    container_name: data3-storage-node-1
    image: kandolanetwork/data3-storage-node:latest
    environment:
      GRAILS_ENV: development
      OBSERVABILITY_SERVER_HOSTNAME: 192.168.5.168
      OBSERVABILITY_SERVER_PORT: 8443
      OBSERVABILITY_SERVER_USERNAME: admin
      OBSERVABILITY_SERVER_PASSWORD: admin
      DBPROXY_ADMIN_USERNAME: admin
      DBPROXY_ADMIN_PASSWORD: admin

      NODE_PROVIDER_BASE_URL: http://192.168.5.168:8080/
      SELF_STORAGE_NODE_HOSTNAME: 192.168.5.168
    volumes:
      - data3-storage-node-volume:/app/data_home
      - ./proxysql.cnf:/etc/proxysql.cnf
    expose:
      - 8080
      - 6033
      - 42000
      - 42001
    ports:
      - "16033:6033"
      - "38080:8080"
      - "42000:42000"
      - "42001:42001"
    networks:
      - data3-storage-node-network
    extra_hosts:
      - "host.docker.internal:host-gateway"
volumes:
  data3-storage-node-volume:
networks:
  data3-storage-node-network:
    driver: bridge

When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new bridge network named data3-storage-node-network.

https://hub.docker.com/r/kandolanetwork/data3-storage-node
Docker Hub Registry
list of available versions