This article is intended for witnesses. It explains a fix laid out by another witness (@abit) applied to a different scenario (Steem-in-a-box), which is a method of running STEEM made by myself.

As docker is a little bit different to running it on the host machine, the fixes laid out in @abit's article are applied differently.

1. Stop your witness

./run.sh stop

2. Increase the SHM size on the host

mount -o remount,size=14G /dev/shm

3. Copy the existing shared memory file to /dev/shm

cp data/witness_node_data_dir/blockchain/shared_memory.* /dev/shm/

4. Set the shared directory in your config.ini file to /shm/

shared-file-dir = /shm/

5. Modify the run.sh file

Find and replace the following line:

docker run $DPORTS -v "$DATADIR":/steem -d --name $DOCKER_NAME -t steem

With this:

docker run $DPORTS -v /dev/shm/:/shm -v "$DATADIR":/steem -d --name $DOCKER_NAME -t steem

6. Delete your old witness container

docker rm {witness,witness_bak,seed}

7. Start the witness again

./run.sh start

Finally:

Check that your witness is functioning. You should see some of the the following messages when you run the logs:

./run.sh logs
...
116547ms th_a       main.cpp:196                  main                 ] Started witness node on a chain with 7808435 blocks.
...
675728ms th_a       application.cpp:488           handle_block         ] Got 2 transactions from network on block 7809007

---

Do you like what I'm doing for STEEM/Steemit?

Vote for me to be a witness - every vote counts.

Don't forget to follow me for more like this.

---