This message was deleted.

Hi @few-jordan-3349! The tmpfs is mounted by the immutable-rootfs module which reads the

/run/cos/cos-layout.env

configuration file. Here is an example how to generate that file with the size set to 25%: https://github.com/rancher/elemental/blob/6e4e5808bc781c920de360353c52738c6fd67272/framework/files/system/oem/01_elemental-rootfs.yaml#L31

hi, ok, if i place the yaml in /system/oem like this:

name: "Customize Rootfs Layout Settings"
stages:
  rootfs:
    - if: '[ ! -f "/run/cos/recovery_mode" ]'
      name: "Layout configuration"
      environment_file: /run/cos/cos-layout.env
      environment:
        OVERLAY: "tmpfs:75%"

is this env variable than applied for all tmpfs mounts? In my case i just want to increase /tmp. Would it be aslo an alternative to just use systemd tmp.mount and change size there?

[Unit]
Description=Temporary Directory /tmp
Documentation=<https://systemd.io/TEMPORARY_DIRECTORIES>
Documentation=man:file-hierarchy(7)
Documentation=<https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems>
ConditionPathIsSymbolicLink=!/tmp
DefaultDependencies=no
Conflicts=umount.target
Before=local-fs.target umount.target
After=swap.target

[Mount]
What=tmpfs
Where=/tmp
Type=tmpfs
Options=mode=1777,strictatime,nosuid,nodev,size=75%%,nr_inodes=1m

thamks for the help!

Hmm, good catch! Seems that

OVERLAY

is only used for the mounting of the overlayfs.

yes, it seems working. I could build with that systemd unit and i got now an increased /tmp mount. I do not see any problems, but i only did a quick test for this.

Nice! Did you write it in a cloud-init stage? or add it to the image?

atm copied in image

Looking at our example in elemental-toolkit I would even say it's better to have it in the image and put it in /etc/systemd/system/tmp.mount

ok, than i keep it that way for now. Thanks for the help! If i get any problems with that i will text here.

No worries! good work on the tmp-mount! Will look into adding some documentation for that!