Openmaptiles-server on Docker - Config
up vote
0
down vote
favorite
I'm trying to customise OpenMaptiles-Server running under Docker. I've NO docker exposure. I've read the docs and they suggest there is a config file for Docker, but what its name is, where it lives seems to be assumed knowledge.
Is there a blog that explains this for absolute novices as the documentation from Klokantech is not very helpful if you have not used these technologies before.
Can somebody let me know where the configuration file lives, what its name is supposed to be and how I get rid of the error about unconfigured /data directory? thanks
openmaptiles
add a comment |
up vote
0
down vote
favorite
I'm trying to customise OpenMaptiles-Server running under Docker. I've NO docker exposure. I've read the docs and they suggest there is a config file for Docker, but what its name is, where it lives seems to be assumed knowledge.
Is there a blog that explains this for absolute novices as the documentation from Klokantech is not very helpful if you have not used these technologies before.
Can somebody let me know where the configuration file lives, what its name is supposed to be and how I get rid of the error about unconfigured /data directory? thanks
openmaptiles
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm trying to customise OpenMaptiles-Server running under Docker. I've NO docker exposure. I've read the docs and they suggest there is a config file for Docker, but what its name is, where it lives seems to be assumed knowledge.
Is there a blog that explains this for absolute novices as the documentation from Klokantech is not very helpful if you have not used these technologies before.
Can somebody let me know where the configuration file lives, what its name is supposed to be and how I get rid of the error about unconfigured /data directory? thanks
openmaptiles
I'm trying to customise OpenMaptiles-Server running under Docker. I've NO docker exposure. I've read the docs and they suggest there is a config file for Docker, but what its name is, where it lives seems to be assumed knowledge.
Is there a blog that explains this for absolute novices as the documentation from Klokantech is not very helpful if you have not used these technologies before.
Can somebody let me know where the configuration file lives, what its name is supposed to be and how I get rid of the error about unconfigured /data directory? thanks
openmaptiles
openmaptiles
asked Oct 19 at 4:04
Gav_at_ASTS
63
63
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Assuming you mean the docker image at klokantech/openmaptiles-server, the method for configuration is as follows:
- Pull the image.
- Run the image - expose a local port you can connect to, and bind-mount a local path to the image at /data
- Run a browser and connect to the container host at the specified port. A 'first time install' interface will come up allowing you select what regions you want to download mbtile data for. Note that you can only run 1 mbtile per server - it will render 'blank' (tan) tiles for everything outside that region. Allow the container server to download the tiles.
- Inspect the local path that was mounted to the container at /data. You should now see a .mbtiles and a config.json file. Save those off somewhere for posterity.
- In the actual location you intend to now run the container, deploy the image, the mbtiles, and the config.json. Put the mbtiles and config.json in the same local directory, and bind mount those to /data when you run the openmap-tileserver. It will pick up on the existing mbtiles and config, skipping the install step, and boot straight into serving the tiles.
H Zach, thanks kindly for your detailed reply. I've now got past the issues I was having. These related primarily to the fact that I had no prior Docker exposure at all. Now that I've had a chance to get up to speed with Docker, things start to make much more sense.
– Gav_at_ASTS
Nov 11 at 23:21
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Assuming you mean the docker image at klokantech/openmaptiles-server, the method for configuration is as follows:
- Pull the image.
- Run the image - expose a local port you can connect to, and bind-mount a local path to the image at /data
- Run a browser and connect to the container host at the specified port. A 'first time install' interface will come up allowing you select what regions you want to download mbtile data for. Note that you can only run 1 mbtile per server - it will render 'blank' (tan) tiles for everything outside that region. Allow the container server to download the tiles.
- Inspect the local path that was mounted to the container at /data. You should now see a .mbtiles and a config.json file. Save those off somewhere for posterity.
- In the actual location you intend to now run the container, deploy the image, the mbtiles, and the config.json. Put the mbtiles and config.json in the same local directory, and bind mount those to /data when you run the openmap-tileserver. It will pick up on the existing mbtiles and config, skipping the install step, and boot straight into serving the tiles.
H Zach, thanks kindly for your detailed reply. I've now got past the issues I was having. These related primarily to the fact that I had no prior Docker exposure at all. Now that I've had a chance to get up to speed with Docker, things start to make much more sense.
– Gav_at_ASTS
Nov 11 at 23:21
add a comment |
up vote
0
down vote
Assuming you mean the docker image at klokantech/openmaptiles-server, the method for configuration is as follows:
- Pull the image.
- Run the image - expose a local port you can connect to, and bind-mount a local path to the image at /data
- Run a browser and connect to the container host at the specified port. A 'first time install' interface will come up allowing you select what regions you want to download mbtile data for. Note that you can only run 1 mbtile per server - it will render 'blank' (tan) tiles for everything outside that region. Allow the container server to download the tiles.
- Inspect the local path that was mounted to the container at /data. You should now see a .mbtiles and a config.json file. Save those off somewhere for posterity.
- In the actual location you intend to now run the container, deploy the image, the mbtiles, and the config.json. Put the mbtiles and config.json in the same local directory, and bind mount those to /data when you run the openmap-tileserver. It will pick up on the existing mbtiles and config, skipping the install step, and boot straight into serving the tiles.
H Zach, thanks kindly for your detailed reply. I've now got past the issues I was having. These related primarily to the fact that I had no prior Docker exposure at all. Now that I've had a chance to get up to speed with Docker, things start to make much more sense.
– Gav_at_ASTS
Nov 11 at 23:21
add a comment |
up vote
0
down vote
up vote
0
down vote
Assuming you mean the docker image at klokantech/openmaptiles-server, the method for configuration is as follows:
- Pull the image.
- Run the image - expose a local port you can connect to, and bind-mount a local path to the image at /data
- Run a browser and connect to the container host at the specified port. A 'first time install' interface will come up allowing you select what regions you want to download mbtile data for. Note that you can only run 1 mbtile per server - it will render 'blank' (tan) tiles for everything outside that region. Allow the container server to download the tiles.
- Inspect the local path that was mounted to the container at /data. You should now see a .mbtiles and a config.json file. Save those off somewhere for posterity.
- In the actual location you intend to now run the container, deploy the image, the mbtiles, and the config.json. Put the mbtiles and config.json in the same local directory, and bind mount those to /data when you run the openmap-tileserver. It will pick up on the existing mbtiles and config, skipping the install step, and boot straight into serving the tiles.
Assuming you mean the docker image at klokantech/openmaptiles-server, the method for configuration is as follows:
- Pull the image.
- Run the image - expose a local port you can connect to, and bind-mount a local path to the image at /data
- Run a browser and connect to the container host at the specified port. A 'first time install' interface will come up allowing you select what regions you want to download mbtile data for. Note that you can only run 1 mbtile per server - it will render 'blank' (tan) tiles for everything outside that region. Allow the container server to download the tiles.
- Inspect the local path that was mounted to the container at /data. You should now see a .mbtiles and a config.json file. Save those off somewhere for posterity.
- In the actual location you intend to now run the container, deploy the image, the mbtiles, and the config.json. Put the mbtiles and config.json in the same local directory, and bind mount those to /data when you run the openmap-tileserver. It will pick up on the existing mbtiles and config, skipping the install step, and boot straight into serving the tiles.
answered Nov 9 at 18:03
Zach Swanson
464
464
H Zach, thanks kindly for your detailed reply. I've now got past the issues I was having. These related primarily to the fact that I had no prior Docker exposure at all. Now that I've had a chance to get up to speed with Docker, things start to make much more sense.
– Gav_at_ASTS
Nov 11 at 23:21
add a comment |
H Zach, thanks kindly for your detailed reply. I've now got past the issues I was having. These related primarily to the fact that I had no prior Docker exposure at all. Now that I've had a chance to get up to speed with Docker, things start to make much more sense.
– Gav_at_ASTS
Nov 11 at 23:21
H Zach, thanks kindly for your detailed reply. I've now got past the issues I was having. These related primarily to the fact that I had no prior Docker exposure at all. Now that I've had a chance to get up to speed with Docker, things start to make much more sense.
– Gav_at_ASTS
Nov 11 at 23:21
H Zach, thanks kindly for your detailed reply. I've now got past the issues I was having. These related primarily to the fact that I had no prior Docker exposure at all. Now that I've had a chance to get up to speed with Docker, things start to make much more sense.
– Gav_at_ASTS
Nov 11 at 23:21
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52885760%2fopenmaptiles-server-on-docker-config%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown