--snip--
I'll try your container next (and I've never used containers before). CPUmining would be fun, I tried it before on testnet, but had to conclude it's impossible. If there's even a single ASIC mining on testnet4, I expect CPUmining to be futile already.
The mining container is ready, it works, but (like you suspected) somebody is already running one (or more) asic's on testnet4.... why... i really wonder why.... why would you run an asic on a network that's designed to test ... why won't you let others get some tBTC to play with... At least, if you're nuking the testnet, create a faucet where others can have some tBTC to test out their setups...
If you need help with containers, let me know... But basically, if you trust what i've done, you could basically install docker and docker-compose on your system, make sure the docker daemon is running (on most linux distro's, a systemd service is created for you, you just need to enable and start it), then copy the content of the docker-compose.yml code block from this post (
https://bitcointalk.org/index.php?topic=5496494.msg64078200#msg64078200) into a local docker-compose.yml file, edit the paths, ports and passwords and execute "docker-compose up" (or "docker-compose up -d" to start in the background)
If you don't trust what i've done (i don't blame you), you could copy the first code block in above post in a file called "Dockerfile" (you can check all steps), then run "docker build -t name_of_image:random_tag .". At this point, you'll have an image of your own in your local repo, and you can edit the image: tag in the docker-compose.yml file to point to your local image instead of mine.