Example Analysis of tmpfs mounts for Docker data Storage

This article mainly introduces the Docker data storage tmpfs mounts example analysis, has a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, the following let the editor take you to understand it.

Tmpfs mounts

The Volumes and Bind mounts modes enable us to share files between the host and the container so that we can persist the data to the host to avoid the problem of data loss after the container is stopped when writing to the container storage layer.

If you use linux to run Docker, there is another solution to avoid writing data to the container storage layer: tmpfs mounts.

Tmpfs mounts, as its name implies, is a non-persistent data store. It only stores the data in the host's memory, and once the container stops running, the tmpfs mounts will be removed, resulting in data loss.

The use of tmpfs mounts

We can use tmpfs mounts when running the container by specifying either the-- tmpfs parameter or the-- mount parameter:

$docker run-d\-it\-- name tmptest\-- mount type=tmpfs,destination=/app\ nginx:latest$ docker run-d\-it\-- name tmptest\-- tmpfs / app\ nginx:latest

You cannot specify any other options using the-- tmpfs parameter and cannot be used with Swarm Service.

Use the docker container inspect tmptest command, and then look at the Mounts section to see:

"Tmpfs": {"/ app": ""}

Tmpfs mounts optional option

An example:

Docker run-d\-it\-- name tmptest\-- mount type=tmpfs,destination=/app,tmpfs-mode=1770\ nginx:latest Thank you for reading this article carefully. I hope the article "sample Analysis of tmpfs mounts for Docker data Storage" shared by the editor will be helpful to you. At the same time, I also hope you will support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!