Nominatim-docker : file does not exist pbf path error in nominatim by using docker image(docker run error) - nominatim

When i am running this command
docker run -it --rm -e PBF_PATH=/nominatim/data/karnataka-latest.osm.pbf -p 8080:8080 -v /root:/nominatim/data/ --name nominatim
mediagis/nominatim:4.0
iam trying to use this PBF_PATH = "my downloaded country.osm.pbf and saved in my local system"
should i change docker image else what would be the solution.
this was an error (last 3 lines)
+ sudo -E -u nominatim nominatim import --osm-file /nominatim/data/karnataka-latest.osm.pbf --threads 16
2022-08-11 09:49:56: Using project directory: /nominatim
2022-08-11 09:49:56: OSM file '/nominatim/data/karnataka-latest.osm.pbf' does not exist.
2022-08-11 09:49:56: FATAL: Cannot access file.
any suggestions please.

Related

Restore .bak file with docker MSSQL server in MAC OS

I am using the docker MS-SQL server latest version and trying to restore the database (.bak) file using Azure data studio. But not able to find the physical location in MAC
As per the Azure data studio it points the data to the /var/opt/mssql/data however, we can't find the location on the MAC OS.
Docker SQL server command that I used to run the image
docker run --name MsSql -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=xxxxxxx' -p 1433:1433 -d mcr.microsoft.com/mssql/server:2019-latest
using the below command solve my issue, I have to mount the volume with the container volumn
docker run --name MsSql -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=FeteBird#sql' -p 1433:1433 -v /var/opt/mssql/data:/var/opt/mssql/data -d mcr.microsoft.com/mssql/server:2019-latest

docker for toolkit documentation: `docker export` not including all layers?

After having given up on other means to document my R analysis environment(s) properely with the aim of analysis reproducibility, I'm setting out, to wrap each individual analysis into a docker container.
Here is what I do:
Pull the latest rstudio container from the rocker project:
docker pull rocker/rstudio
Create a project-specific copy
docker run -d -p 8787:8787 rocker/rstudio # Produces baseID
docker commit --message="Snapshot of current rocker/rstudio container" <baseID> rstudio_project.2018
docker stop <baseID>
Fire up the container:
docker run -d -p 8787:8787 -e ROOT=TRUE rstudio_project.2018 # produces ID
R(Studio)- based project analysis ... finishing with sudo apt-get clean and sudo rm -rf /tmp/*
Export a docker image:
docker export -o docker_rstudio_project.2018.tar <ID>
xz docker_rstudio_project.2018.tar
After having deleted all related containers/images from my local registry, I try to emulate the revisit of the packaged project like so:
Import the container:
docker import docker_rstudio_project.2018.tar.xz rstudio_project.2018.2
(Try to) Fire up container as was done for the original:
docker run -d -p 8787:8787 -e ROOT=TRUE rstudio_project.2018.2
I am then faced with the following error:
docker: Error response from daemon: No command specified.
What am I doing wrong? Where did the container loose (what) information on what to start by default?
The export and import commands only handle the file system, not metadata like what command to run. Use save and load instead. See also https://github.com/moby/moby/issues/1826

run rscript on local in a docker image

I have pulled a kaggle/rstats image on my local windows machine. I want to run a local code script.r in the kaggle image.
My code script.r is stored in "D:/codes/script.r." I have installed docker and pulled kaggle/rstats image in "E:/docker."
Can somebody please help with how to run script.r in kaggle docker image.
I have been using the following command to run it but of course there is some issue with it which I can't figure out.
docker run -v $PWD:D:/codes -w=D:/codes --rm -it kaggle/rstats Rscript script.r
Output:
docker: Error response from daemon: Invalid bind mount spec "/c/Users/Rohan:D:/codes": invalid mode: /codes.
See 'E:\Docker Toolbox\docker.exe run --help'.
I tried following as well:
docker run -v /D:/codes -w=/D:/codes --rm -it kaggle/rstats Rscript script.r
Output:
Fatal error: cannot open file 'script.r': No such file or directory
script.r is present in D:/codes, not sure why it is saying no such file.
What is wrong in the command?

Docker and Analytics Install

I have a docker file called quasar.dockerfile. I built the docker file and everything loaded successfully.
#quasar.dockerfile
FROM java:8
WORKDIR /app
ADD docker/quasar-config.json quasar-config.json
RUN apt-get update && \
apt-get install -y wget && \
wget https://github.com/quasar-analytics/quasar/releases/download/v2.3.3-SNAPSHOT-2121-web/web_2.11-2.3.3-SNAPSHOT-one-jar.jar
EXPOSE 8080
CMD java -jar web_2.11-2.2.3-SNAPSHOT-one-jar.jar -c /app/quasar-config.json
I then tried running the docker and I get this error saying that I am unable to access the jarfile.
[test]$ docker build -f docker/quasar.dockerfile -t quasar_fdw_test/quasar .
Sending build context to Docker daemon 1.851 MB
Successfully built a7d4bc6c906f
[test]$ docker run -d --name quasar_fdw_test-quasar --link quasar_fdw_test-mongodb:mongodb quasar_fdw_test/quasar
6af2f58bf446560507bdf4a2db8ba138de9ed94a408492144e7fdf6c1fe05118
[test]$ docker ps -l
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6af2f58bf446 quasar_fdw_test/quasar "/bin/sh -c 'java -ja" 5 seconds ago Exited (1) 4 seconds ago quasar_fdw_test- quasar
[test]$ docker logs 6af2f58bf446
Error: Unable to access jarfile web_2.11-2.2.3-SNAPSHOT-one-jar.jar
How come the process keeps getting killed? Seems like it has to do with being unable to run the jarfile but the build needed to access that file and happened successfully. Is this a linking issue?
Try to use full path on Dockerfile
CMD java -jar /web_2.11-2.2.3-SNAPSHOT-one-jar.jar -c /app/quasar-config.json

Error when trying to run a meteor app in docker using meteorhacks:meteord

I have just began playing around with docker. While trying out method 1 from meteorhacks:meteord, I get the folowing error
=> You don't have an meteor app to run in this image.
Here is what I have done after creating the basic counter demo meteor app.
docker build -t app .
Sending build context to Docker daemon 11.75 MB
Step 0 : FROM meteorhacks/meteord:base
---> 528baf8d4263
Step 1 : MAINTAINER MeteorHacks Pvt Ltd.
---> Running in 6d7e7eb6ebce
---> d69fefdbeb70
Removing intermediate container 6d7e7eb6ebce
Step 2 : ONBUILD copy ./ /app
---> Running in e68618104dfa
---> c253ae966ea1
Removing intermediate container e68618104dfa
Step 3 : ONBUILD run bash $METEORD_DIR/on_build.sh
---> Running in e51e557c2b05
---> a6a6a1be9147
Removing intermediate container e51e557c2b05
Successfully built a6a6a1be9147
then ( I already initiated a mongo container exposing 27017 and grabbed the internal ip address which was 171.17.0.1)
docker run -d \
-e ROOT_URL=http://localhost:3000 \
-e MONGO_URL=mongodb://172.17.0.1:27017/ \
-e MONGO_OPLOG_URL=mongodb://172.17.0.1:27017/ \
-p 8080:80 \
app
I get the error when I do this and then run docker logs <container id>
Can someone guide me on this?
Thanks in advance.
This error comes from scripts/run_app.sh, which is the ENTRYPOINT of the base Dockerfile.
It checks for the presence of:
/bundle folder, or
/built_app, or
$BUNDLE_URL
If your counter demo Dockerfile didn't populate /bundle or /built_app folders, then you need to make sure you are defining ENV BUNDLE_URL with the right url.

Resources