Skip to content
This repository has been archived by the owner on May 7, 2020. It is now read-only.

Proper way to run built container? #10

Open
fjsj opened this issue Oct 23, 2018 · 2 comments
Open

Proper way to run built container? #10

fjsj opened this issue Oct 23, 2018 · 2 comments

Comments

@fjsj
Copy link

fjsj commented Oct 23, 2018

That's an amazing project, thanks!

I'm having some trouble to figure out the proper way to run the built container.

The recommended command
docker run --restart=always -d -p 80:80 merlinnot/nominatim-docker
fails with the following message:

Unable to find image 'merlinnot/nominatim-docker:latest' locally
docker: Error response from daemon: manifest for merlinnot/nominatim-docker:latest not found.
See 'docker run --help'.

If I do:
sudo docker run --restart=always -d -p 80:80 nominatim
It works, but the base href on HTML is set to the container ID, like: <base href="http://457fa9e123ba/" />

So, there seem to be two problems here:

  • merlinnot/nominatim-docker name doesn't work?
  • base href config is broken? CONST_Website_BaseURL should have hostname?

I was able to get around those problems by manually setting the container hostname:
sudo docker run --restart=always -h 222.22.111.111/nominatim -d -p 80:80 nominatim
Perhaps you want to document this?

@fjsj
Copy link
Author

fjsj commented Oct 23, 2018

Also, that's causing me trouble to run Nominatim on https. I'm using a nginx proxy in front of it, but I can't make the base href to have the https prefix.

@merlinnot
Copy link
Owner

Hi, you need to run it with sudo only because of your local Docker setup. Take a look at post-install steps.

I’ll take a look at the rest of the issues later today.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants