coreos / coreos/coreos-assembler

Max override file size for custom "cosa build"?

Open
#4,071 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
393
Forks
193
Avg merge
17h 6m
Merged PRs (30d)
5

Description

Bug Report

There's a silent, and very frustrating, size limit on override files, and this includes files IN rpms.

I've tried a hell of combos and endless builds, but the short of it is I've been trying to build the coreos live iso with a smallish prepackaged docker image file.

Basically, at this point I have an rpm with 4 files in it, two are docker image files. One is 101MB the other is 19MB. Not a lot of bulk, but its something I need to include in this ISO for it to be useful post install.

The rpm spec stuffs the two docker image files it into, and my rpm is put into the fcos/overrides/rpms folder so they make their way into the live ISO for install.

This basically works, except the two large-ish files are missing. I can't grab the console output easily right now but it goes like this:

$ rpm -ql testo
/usr/lib/systemd/system/teso.service
/var/lib/testo/images/test1.tar.gz
/var/lib/testo/images/test2.tar.gz

ls -al /var/lib/testo/images/
<nothing, nothing as sudo or root>

Is there some silent file limit? Can I bypass or change it?

My workaround was to have the rpm .spec SPLIT the files into 5MB chunks, then in the .service I include in the rpm, I cat them into "docker load". This imports the image fine. But this is crazy.

I had also hoped to bypass the rpm altogether and just dump my files into fcos/overrides/rootfs, but likely because it too suffers from the file size limit, I spent a 1/2 a day trying to figure out why my files weren't appearing in the ISO or install!? Now I know. Too big.

Environment

What operating system is being used to run coreos-assembler?
Fedoras 41, using quay.io/coreos-assembler/coreos-assembler:latest, f241c9fcd029, pulled 10 hours ago

What operating system is being assembled?
Coreos? Whatever the latest is. The build is fairly on rails.

Is coreos-assembler running in Podman or Docker?
Podman

If Podman, is coreos-assembler running privileged or unprivileged?
Doesn't matter, the build works.

Expected Behavior

Let me override the file limit. There's not much reason to impose this limit, or hide it.

Actual Behavior

Files over 10MB(?) are skipped in the cosa build, even when they're in an override rpm and it installed the rpm without warning or complaint or exception. Just install the files.

Reproduction Steps

Other Information

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the build with files larger than 10 MB in fcos/overrides/rpms and fcos/overrides/rootfs, using the reported coreos-assembler container setup, and inspect the build output for skipped files. Trace the override-file handling from cosa build to determine whether the limit is documented or configurable; done means oversized files are either included or rejected with a clear diagnostic.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
build-system, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.