mediciland/flocore repository overview

⁠Docker FLO Core

This image runs the official FLO Core full node and optionally exposes an RPC connection.

⁠Available Versions

You can see all images available to pull from Docker Hub via the Tags page⁠.

⁠Usage Example

docker volume create flocore

docker run -d --name=flocore \
	-p 17313:17313 --mount source=flocore,target=/data \
	--env NETWORK=testnet --env ADDNODE=35.230.92.250 \
	--env RPC=true --env RPC_USER=flo --env RPC_PASSWORD=test1234 \
	mediciland/flocore

docker logs -f flocore

⁠Environment Variables

FLO Core uses Environment Variables to allow for configuration settings. You set the Env Variables in your docker run startup command. Here are the config settings offered by this image.

• NETWORK: [mainnet|testnet|regtest] The FLO network you wish to run on (Default mainnet).
• ADDNODE: [ip-address] An IP address of a FLO node to be used as a source of blocks. This is useful if you are running isolated networks, or if you are having a hard time connecting to the network.
• RPC: [true|false] Should FLO Core allow RPC connections (Default false).
• RPC_USER: [String] The RPC username for the FLO Core full node running inside the container.
• RPC_PASSWORD: [String] The RPC password for the FLO Core full node running inside the container. You can modify this for a small improvement in security.
• GENERATE_BLOCKS_INTERVAL: [String] The interval at which you wish to generate new regtest blocks. (Example, 40s)
• CUSTOM_FLO_CONFIG: [String] A string (seperated with \n to split lines lines) of extra config variables to add to flo.conf

⁠Security Reports

Please email [email protected]⁠ with security concerns.

⁠Maintainers