RSK
EVM sidechain for Bitcoin
RSK is configured by default to accept only localhost / 127.0.0.1 as the hostname
So when StackOS provides a custom hostname, or you configure your own DNS, RSK will refuse to serve any jsonrpc responses

Solution

Prepare node.conf

Take the default node.conf and change the hosts the image will recognize
1
web: {
2
cors: "*",
3
http: {
4
enabled: true,
5
bind_address = "0.0.0.0",
6
hosts = ["tagethost.example.com"]
7
port: 4444,
8
}
9
ws: {
10
enabled: false,
11
bind_address: "0.0.0.0",
12
port: 4445,
13
}
14
}
15
}
16
Copied!

Make a Dockerfile

1
FROM mainnet:latest
2
COPY node.conf /etc/rsk/node.conf
Copied!

Build & push your image

1
docker build -t dockerhubuser/myrsk:v123
2
docker push dockerhubuser/myrsk:v123
Copied!

Configure your pod

Download your own image that you just uploaded
If you want to use custom DNS, set that up ahead of time

Test your connection

Run curl against your host
1
curl https://rsk.mydomain.com/mainnet --header 'Content-Type: application/json' -XPOST -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'
Copied!
Expect a response like
1
{"jsonrpc":"2.0","id":1,"result":"0x0"}
Copied!

Debug your pod

Edit /etc/rsk/logback.xml and increase verbosity for jsonrpc
Wait 1 hour for rsk to read your new log config (or rebuild your docker image and force the change)
Watch for error messages
1
tail -f /var/log/rsk/rsk.log | grep rpc
Copied!

Persistent Storage

If you wish to use persistent storage with rsk, be aware you must update the permissions of the storage directory
Here is an example configuraton
After your pod boots, locate your pod name and shell into your pod:
Then run the following command
1
chown -R rsk:rsk /var/lib/rsk
Copied!
Then your process will run normally.