symlinking BalenaOS to SSD to prevent no disk space left when updating container

Hi everyone,

I have a Jetson Xavier NX production module with 16GB EMMC on a Avermedia EN713-AAE9-0000 carrier board. I added a 256Gb ssd to SATA for extra storage. Because 16GB is just enough for Ubuntu CUDA containers, but sometimes updating causes issues, because of not enough diskspace. I think delta updates make a copy of the image and then apply the delta update. Is this correct?

I was wondering if I could somehow mount and simlink a directory on BalenaOS to prevent not enough diskspace issues. My first thought would be a udev rule and mount drive and then execute bash to do the deed.

/etc/udev/rules.d/70_hot-swap-mount.rules:

  # to create mount-points and mount devices
  KERNEL=="sd[a-z][0-9]", ENV{ID_MODEL_ID}=="fill-in-model-id-here", ENV{ID_VENDOR_ID}=="fill-in-vendor-id-here", ACTION=="add", ENV{mount_options}="relatime", RUN+="/bin/mkdir -p /media/disk0Z", RUN+="/bin/mount -o $env{mount_options} /dev/%k /media/disk0Z"

  # to unmount devices and remove mount-points
  KERNEL=="sd[a-z][0-9]", ENV{ID_MODEL_ID}=="fill-in-model-id-here", ENV{ID_VENDOR_ID}=="fill-in-vendor-id-here", ACTION=="remove", RUN+="/bin/umount -l /media/disk0Z", RUN+="/bin/rmdir /media/disk0Z" 

And I found this:

My question is. Is this good practice? And which directory should I symlink?