Issues starting elasticsearch using Docker with Haystack utility function

[OMGAmici]

I am trying to follow along with this tutorial to create a QA system. I have Docker downloaded to my machine and am using a Jupyter notebook. Whenever I try to start elasticsearch using the recommended Haystack utility function, I get an error that it failed.

WARNING - haystack.utils.doc_store - Tried to start Elasticsearch through Docker but this failed. It is likely that there is already an existing Elasticsearch instance running.

The line I am trying to run: launch_es()

I am able to start a Docker image for elasticsearch just fine using:
!docker pull docker.elastic.co/elasticsearch/elasticsearch:7.9.2
!docker run -d -p 9200:9200 -e "discovery.type=single-node" elasticsearch:7.9.2

I should also add that I've also confirmed there are no instances running in Docker Desktop.

[bglearning]

Hi,
Could you check directly if there is an ES instance running? (perhaps with curl localhost:9200)

[OMGAmici]

Can you give me a some more guidance on exactly how I can check this? I am not very familiar with troubleshooting this sort of thing, so any extra details would be very appreciated, thank you!

!curl localhost:9200 returns an error that the connection was refused when I try to run it from my Jupyter notebook

[OMGAmici]

docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create?name=elasticsearch": dial unix /var/run/docker.sock: connect: permission denied.
See 'docker run --help'.
WARNING:haystack.utils.doc_store:Tried to start Elasticsearch through Docker but this failed. It is likely that there is already an existing Elasticsearch instance running. 

This is the new error message I am receiving. I reinstalled Docker on my Ubuntu and tried running launch_es() from the Jupyter notebook again.

[bglearning]

Hmm... do the direct !docker ... still run fine now after the reinstallation?
It could be that you might have to follow the post-installation process for docker. Also here.