Solution:
From your error message, the EADDRINUSE strikes port 80 is meanwhile in use on either the docker VM or probably directly on your laptop. You can either stop whatever is running on that port, or alter the port employed in your Docker, command. To alter to the external port 8080, Employ:
docker run -d -p 8080:80 --name webserver nginx
I had the similar problem with one of my containers. I attempted everything however at the time nothing performed, I attempted the following and launched the container again with success
sudo service docker stop
sudo rm /var/lib/docker/network/files/local-kv.db
sudo service docker start
Latterly this issue started to occur a lot on Windows. You can attempt restarting docker or you can manually stop docker before Windows shutdown - docker begins cleanly on reboot.
Stop all the running containers docker ps -a -q thereafter Stop the Docker on your machine & restart it.
I got past most of the hurdles bar one. I copied reJSON employing git then compiled the module, then added it in the redis.conf file.
Now the one hurdle left which is possibly the same as what the logs in my post above also tell, where it couldn't connect to IP/port 0.0.0.0:6379 as it was in exercise meanwhile.
redis.conf has "bind 127.0.0.1" defined. At the time including in the line "loadmodule /path/to/file/rejson.so" (where /path/to/file/ is the correct path), the redis-cli command doesn't link, with the loadmodule command commented out I can link with redis-cli to 127.0.0.1:6379 fine
