# Reduce Update size

**URL:** <https://universal-blue.discourse.group/t/reduce-update-size/2147>\
**Category:** Bazzite\
**Created:** [June 6, 2024, 9:30am UTC](https://universal-blue.discourse.group/t/reduce-update-size/2147 "2024-06-06T09:30:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DocMAX](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/docmax/32/2010_2.png) [@DocMAX](https://universal-blue.discourse.group/u/DocMAX)\
**Post date:** [June 6, 2024, 9:30am UTC](https://universal-blue.discourse.group/t/reduce-update-size/2147/1 "2024-06-06T09:30:40Z")

</div>

I have 5 handhelds and updating is a pain when it comes to the file sizes. 4+ GB for each device for (by default, yes i know i can change that) 2 days. That’s too much. I heard work is being done here. Where can i inform or contribute to the progress?

---

<div class="post-metadata">

**Author:** ![j0rge](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/j0rge/32/8_2.png) [@j0rge](https://universal-blue.discourse.group/u/j0rge)\
**Post date:** [June 6, 2024, 12:00pm UTC](https://universal-blue.discourse.group/t/reduce-update-size/2147/2 "2024-06-06T12:00:57Z")

</div>

Here’s the overall roadmap:

> **[Roadmap to Fedora Bootable Containers (#26) · Issues · fedora / Fedora Atomic...](https://gitlab.com/fedora/ostree/sig/-/issues/26)**
>
> Important initial notes This is a proposed roadmap that is subject to change and refinement While not complete...

And the issues in particular for downloads:

> <https://github.com/containers/bootc/pull/215>
>
> Prep in https://github.com/containers/bootc/pull/214Move pull code into deploy
> …
> \---
> 
> WIP: Use \`podman pull\` to fetch containers
> 
> See https://github.com/containers/bootc/issues/147#issuecomment-1828751377
> 
> With this bootc starts to really gain support for a different backend
> than ostree. Here we basically just fork off \`podman pull\` to
> fetch container images into an \*alternative root\* in
> \`/ostree/container-storage\`,
> (Because otherwise basic things like \`podman image prune\` would
> delete the OS image)
> 
> This is quite distinct from our use of \`skopeo\` in the ostree-ext project
> because suddenly now we gain support for things
> implemented in the containers/storage library like \`zstd:chunked\` and
> OCI crypt.
> 
> \*However\*...today we still need to generate a final flattened
> filesystem tree (and an ostree commit) in order to maintain
> compatibilty with stuff in rpm-ostree. (A corrollary to this is
> we're not booting into a \`podman mount\` overlayfs stack)
> Related to this, we also need to handle SELinux labeling.
> 
> Hence, we implement "layer squashing", and then do some final
> "postprocessing" on the resulting image matching the same logic
> that's done in ostree-ext such as \`etc -\> usr/etc\` and handling \`/var\`.
> 
> Note this also really wants
> https://github.com/ostreedev/ostree/pull/3106
> to avoid duplicating disk space.
> 
> \---

And you’ll see a bunch of interconnected issues there. I’m now publishing bluefin containers with zstd:chunked to help with testing: [Package bluefin · GitHub](https://github.com/ublue-os/bluefin/pkgs/container/bluefin)