I observed that the size of the tmpfs volumes created by docker is roughly half the size of the machine's physical memory.
For example, on a machine with 22GB of RAM, I got this:
Filesystem Size Used Avail Use% Mounted on
overlay 970G 130G 840G 14% /
tmpfs 64M 0 64M 0% /dev
tmpfs 12G 0 12G 0% /sys/fs/cgroup
tmpfs 20G 0 20G 0% /ramdisk
/dev/sda1 970G 130G 840G 14% /etc/hosts
tmpfs 12G 180K 12G 1% /dev/shm
tmpfs 12G 0 12G 0% /proc/acpi
tmpfs 12G 0 12G 0% /proc/scsi
tmpfs 12G 0 12G 0% /sys/firmware
I would like to increase this size. Could anybody please tell me how to do that?
Thank you very much in advance for your help!
Update: Let me add some context to this question.
In my docker I have a /ramdisk volume whose size is large (here 20GB) because one of my programs needs that:
nvidia-docker run --ipc=host -h $HOSTNAME --mount type=tmpfs,destination=/ramdisk,tmpfs-mode=1770,tmpfs-size=21474836480
When running the program, at the moment its memory usage surpasses 12GB of ramdisk, it crashes (while ramdisk still has 8GB left). Note that 12GB is the size of the other tmpfs system volumes.
So, one solution I could think of is to increase the size of those other volumes, which is my question.
As per docker docs (20GiB as per example):
docker run -d \
-it \
--name tmptest \
--mount type=tmpfs,destination=/app,tmpfs-mode=1770,tmpfs-size=21474836480 \
nginx:latest
PS: Docs specify that by default tmpfs volumes have unlimited size, so the calculations here might be rounded down to the amount of free memory in the host OS.
SRC: https://docs.docker.com/storage/tmpfs/#specify-tmpfs-options
Related
I'm using the https://github.com/lukechilds/dockerpi project to recreate a Raspberry Pi locally with Docker. However, the default disk space is very small and I quickly fill it up:
pi#raspberrypi:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 1.8G 1.2G 533M 69% /
devtmpfs 124M 0 124M 0% /dev
tmpfs 124M 0 124M 0% /dev/shm
tmpfs 124M 1.9M 122M 2% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 124M 0 124M 0% /sys/fs/cgroup
/dev/sda1 253M 52M 201M 21% /boot
tmpfs 25M 0 25M 0% /run/user/1000
How can I give move space to the RPi? I saw this issue, but I don't understand how that solution is implemented, or if it is relevant.
To increase the disk size, you need to extend the partition of the qemu disk used inside the container.
Start the docker to unzip rootfs and mounted it to an host path
docker run --rm -v $HOME/.dockerpi:/sdcard -it lukechilds/dockerpi
When the virtualized raspberry is up, you can stop it, running from the docker prompt sudo poweroff
Then you have the qemu disk in $HOME/.dockerpi/filesystem.img.
It could be extended with :
sudo qemu-img resize -f raw $HOME/.dockerpi/filesystem.img 10G
startsector=$(fdisk -u -l $HOME/.dockerpi/filesystem.img | grep filesystem.img2 | awk '{print $2}')
sudo parted $HOME/.dockerpi/filesystem.img --script rm 2
sudo parted $HOME/.dockerpi/filesystem.img --script "mkpart primary ext2 ${startsector}s -1s"
Restart the raspberry that will use the resized qemu disk with :
docker run --rm -v $HOME/.dockerpi:/sdcard -it lukechilds/dockerpi
Running from the docker prompt you can extend the root filesystem with :
sudo resize2fs /dev/sda2 8G
Finally the root is increased.
Following this df -h give :
Filesystem Size Used Avail Use% Mounted on
/dev/root 7.9G 1.2G 6.4G 16% /
devtmpfs 124M 0 124M 0% /dev
tmpfs 124M 0 124M 0% /dev/shm
tmpfs 124M 1.9M 122M 2% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 124M 0 124M 0% /sys/fs/cgroup
/dev/sda1 253M 52M 201M 21% /boot
tmpfs 25M 0 25M 0% /run/user/1000
If the solution is indeed to resize /dev/root, you can follow this thread, which concludes:
Using the gparted live distro, I struggled for a little while until I realised that the /dev/root partition was within another partition.
Resizing the latter, then the former, everything works. I just gave the /dev/root partition everything remaining on the disk, the other partitions I left at their original sizes.
I was trying to share my GPGPU workstation with some friends. As they are using different environments, I was considering to using docker containers.
When running df -h in docker container, I find:
Filesystem Size Used Avail Use% Mounted on
overlay 10G 24K 10G 1% /
tmpfs 64M 0 64M 0% /dev
tmpfs 3.8G 8.1M 3.8G 1% /run
tmpfs 3.8G 0 3.8G 0% /tmp
tmpfs 3.8G 0 3.8G 0% /run/lock
/dev/sda3 465G 6.2G 459G 2% /etc/hosts
shm 64M 0 64M 0% /dev/shm
tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup
I was surprised to find that /dev/sda3 was mounted on /etc/hosts with host disk size visible. I was not willing to that be seen.
Though it can be umount by rc.local script or some service, but is there any method to avoid docker automatically mount it, let it managed absolutely by container, just like a normal virtual machine?
Docker version is 18.09.6, build 481bc77
Docker container was started by:
docker run -it --net=macvlan -d --cap-add=SYS_ADMIN --tmpfs /tmp --tmpfs /run --tmpfs /run/lock -v /sys/fs/cgroup:/sys/fs/cgroup:ro -e "container=docker" --device /dev/fuse -v /dev/hugepages:/dev/hugepages --runtime=runc --storage-opt "size=10G" ubuntu:16.04 /sbin/init
Dockerfile automatically fetched from docker hub without any change.
https://hub.docker.com/_/ubuntu
https://github.com/tianon/docker-brew-ubuntu-core/blob/010bf9649b1d10e2c34b159a9a9b338d0fdd4939/xenial/Dockerfile
I have a question. Our docker server was out of space for its containers so I gave it a bigger disk from 500GB to 1TB(its a vm) Ubuntu sees this correctily. If I do the command vgs I get this output:
VG #PV #LV #SN Attr VSize VFree
Docker-vg 1 2 0 wz--n- 999.52g 500.00g
But Docker still thinks it's out of space. I have rebooted the docker VM but still he thinks it's out of space. If I use the df -h command this is the output:
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 792M 8.6M 783M 2% /run
/dev/mapper/Docker--vg-root 490G 465G 0 100% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/xvda1 472M 468M 0 100% /boot
As you see the docker-vg still thinks its 490gb
I don't know where to look. can someone help me ?
You still need to extend your logical volume and resize the filesystem to use the larger logical volume.
First, with lvextend, I'm not sure if it works with /dev/mapper. If not, you can do an lvdisplay to list your logical volumes:
lvextend -l +100%FREE /dev/mapper/Docker--vg-root
With ext*fs you can then run a resize:
resize2fs /dev/mapper/Docker--vg-root
The command is similar for xfs:
xfs_growfs /dev/mapper/Docker--vg-root
With "docker system prune" you clean some space removing old images and other stuff.
If you want your container to be aware of the disk size change, you have to:
docker rmi <image>
docker pull <image>
I am using Vagrant with Docker provision.
The issue is when I run my docker compose I fill up my VM disk space.
Here is what my file system looks like:
Filesystem Size Used Avail Use% Mounted on
udev 476M 0 476M 0% /dev
tmpfs 97M 3.1M 94M 4% /run
/dev/sda1 9.7G 2.2G 7.5G 23% /
tmpfs 483M 0 483M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 483M 0 483M 0% /sys/fs/cgroup
tmpfs 97M 0 97M 0% /run/user/1000
vagrant_ 384G 39G 345G 11% /vagrant
vagrant_www_ 384G 39G 345G 11% /vagrant/www
How can I configure Docker or Vagrant to use /vagrant directory?
(By the way I have not loaded Docker... This is why it's not 100% disk usage)
You can try to reconfigure the Docker daemon as documented here -> https://docs.docker.com/engine/reference/commandline/dockerd/#options. Use the -g parameter to change the root runtime path of the Docker daemon.
--graph, -g /var/lib/docker Root of the Docker runtime
As long as you are working on a local disk or SAN this would be a proper way to change the location of the Docker data including the images. But be aware, do not use NFS or another type of share because this won't work as of the used massive file locks. Somewhere on Github there is an issue about this.
I am starting a jenkins container like this, from a local repository:
docker run -d -p 8080:8080 -v /home/docker:/var/jenkins_home 192.168.99.101:5000/jenkins
the output of my container filesystem is like this:
Filesystem Size Used Avail Use% Mounted on
none 19G 3.7G 14G 22% /
tmpfs 499M 0 499M 0% /dev
shm 64M 0 64M 0% /dev/shm
tmpfs 499M 0 499M 0% /sys/fs/cgroup
tmpfs 897M 801M 97M 90% /var/jenkins_home
/dev/sda1 19G 3.7G 14G 22% /etc/hosts
As can be seen, /var/jenkins_home is getting full. How can I increase the size of "tmpfs"?
When you start the container, folder /var/jenkins_home is mounted from your local host's /home/docker, as below option:
-v /home/docker:/var/jenkins_home
So if you clean the space in localhost:/home/docker, you will get more available space.