Add bind mount to Dockerfile just like volume

A Dockerfile defines how an image is built, not how it's used - so you can't specify the bind mount in a Dockerfile. Try using docker-compose instead. A simple docker-compose.yml that mounts a directory for you would look like this:

version: '3.1'services:  mycontainer:    image: myimage    build: .    volumes:      - './path/on/docker/host:/path/inside/container'  

The build: . is optional if you're building the image by some other means, but sometimes it's handy to do it all in one.

Run this with docker-compose up -d

In addition to what the other answers say:

Because bind mounts provide access to the host filesystem, allowing them to be embedded into an image would be a huge security risk. Consider an image that purports to be, say, a web server, but in fact bind mounts your /etc/passwd and /etc/shadow and then sends them off to a remote server.

Or one that bind mounts /lib/ld-linux.so and then overwrites it, thus breaking your entire system.

For these reasons, you cannot embed a a bind mount in your Dockerfile. Similarly, you cannot specify host port mappings, host device access, or any other similar attributes in the Dockerfile.

Simple answer is no.

A basic design principle for docker images is portablility. Bind mounts are hosts specific since the mounted folder is defined on the host machine. Thus this contradicts with the portablility requirement for Docker images.