Not sure what you are saying, but I couldn't change the pool when I specified the 'pool=' in the docker command as provided in the example on the first post.
regards
Hi, first time on STH but been a lurker for years; great website, love the benchmarks, love your direction, love the open source.
I just wanted to confirm, I have the same problem with a bunch of physical and virtual machine - my usual choice is nanopool and I kinda' hate dwarfpool mainly because doesn't even show all my miners so I don't know if they are mining in fact even if the miner is reporting OK.
Point being that for a long time if you set any nanopool pool in the universal container (previously working) just hangs and throws an error like it's stuck with the dwarfish stuff. So have to default for dwarfpool... hate it, really.
Here is the command:
Code:
docker run -it -e username=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXTHEWALLETADDRESSXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -e workerid=PC -e pool=xmr-eu2.nanopool.org -e startport=14444 -e numthreads=4 --cpuset-cpus="0-3" servethehome/universal_cryptonight:latest
Here are the last bits, and that's the point the miner freezes, nothing else gets displayed:
Code:
[100%] Built target xmrig
$donate is empty
* VERSIONS: XMRig/2.6.2 libuv/1.18.0 gcc/7.3.0
* CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (1) x64 AES-NI
* CPU L2/L3: 1.0 MB/8.0 MB
* THREADS: 4, cryptonight, av=0, donate=0%
* POOL #1: stratum+tcp://xmr-usa.dwarfpool.com:14444
* COMMANDS: hashrate, pause, resume
[2018-09-18 08:50:26] READY (CPU) threads 4(4) huge pages 0/4 0% memory 8.0 MB