sonic-buildimage/onie-image.conf
abdosi 9244925943
[baseimage]: incrase docker ramfs from 900MB to 1300MB (#4800)
Images built from 201911 branch and installed on devices where we mount /var/lib/docker in RAM (because the HDD is small) were failing as there was not enough space to untar docker.tar.gz . This is due to the increase in total number of containers in the image.

As of today, /var/lib/docker contains 1.1 GB of data. Therefore, this PR increases the size of the ramdisk to 1.3 GB to accommodate all the containers as of now and any new container going forward.
Example output below from an Arista-7050-QX32 SKU:

admin@str-a7050-acs-2:~$ df -h
Filesystem Size Used Avail Use% Mounted on
.....
tmpfs 1.3G 1.1G 221M 84% /var/lib/docker
.....
Verified all docker running fine and interfaces/bgp are up.

Signed-off-by: Abhishek Dosi <abdosi@microsoft.com>
2020-06-18 10:21:01 -07:00

50 lines
1.1 KiB
Plaintext

## DESCRIPTION:
## config for ONIE image
##
## Partition size in MB
## The default size is 32GB
: ${ONIE_IMAGE_PART_SIZE:=32768}
## Target hardware information
: ${TARGET_PLATFORM:=x86_64}
: ${TARGET_MACHINE:=generic}
ONIEIMAGE_VERSION=r0
## Filename for squashfs file system
FILESYSTEM_SQUASHFS=fs.squashfs
## Filename for onie installer payload, will be the main part of onie installer
ONIE_INSTALLER_PAYLOAD=fs.zip
## Filename for docker file system
FILESYSTEM_DOCKERFS=dockerfs.tar.gz
## docker directory on the root filesystem
DOCKERFS_DIR=docker
## docker ramfs disk space
DOCKER_RAMFS_SIZE=1300M
## Output file name for onie installer
OUTPUT_ONIE_IMAGE=target/sonic-$TARGET_MACHINE.bin
## Output file name for raw image
OUTPUT_RAW_IMAGE=target/sonic-$TARGET_MACHINE.raw
## Raw image size in MB
RAW_IMAGE_DISK_SIZE=2048
## Output file name for kvm image
OUTPUT_KVM_IMAGE=target/sonic-$TARGET_MACHINE.img
## Kvm image size in GB
KVM_IMAGE_DISK_SIZE=16
## Output file name for aboot installer
OUTPUT_ABOOT_IMAGE=target/sonic-aboot-$TARGET_MACHINE.swi
## Aboot boot image name
ABOOT_BOOT_IMAGE=.sonic-boot.swi