-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Requirements #1
Comments
Are you running the docker-compose file, or just the docker image itself? If you are running compose, that will provide MongoDB. However if you are running just the docker image, you will need to provide a running MongoDB server and update the connection url in |
I'll make it so you can provide an ENV var to update those values so it's easier to run the base image. |
Interesting - it does appear that there are known oddities with the DNS resolver and Docker on Windows. Can you confirm that the mongo container is starting correctly? It also appears that there may be a firewall rule to adjust. https://forums.docker.com/t/embedded-dns-not-working/38425/2 What version of Docker are you using? |
Accidentally got too much screenshot in there - it's a Debian VM that I just spun up for this. Docker CE 19.03.4.
If I do
Looks like MongoDB is starting then immedietly stopping - I'm not too familiar with Docker in general so I'm not sure what's causing it. The logs show this:
Looks like a permissions issue but I wouldn't know how I would go about fixing it. |
OK - I found a solution on a forum somewhere. I added an extra bit to the compose file which gave mongo full access to the /bitnami/ directory. https://github.com/JonathanTF2/internet-speed-logger/blob/master/docker-compose.yml Now I've done that Mongo opens fine and everything opens! Only issue I've got now is that the "speedlogger-runner" container is erroring saying it can't find Speedtest:
I've put speedtest from the tar archive in the /bin/ directory and it runs fine on host. |
Great solution! I'll make sure that is noted in the readme. As for the command not found, did you change the path of the |
I'm trying to get this running on a Debian server- the docker image doesn't seem to work on it's own (I'm getting an error connecting to mongodb and the container just keeps restarting, it's been like that for a while now)
Do I need to also clone this repo or install mongo myself?
The text was updated successfully, but these errors were encountered: