Skip to content

Document sandbox limits #1081

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nforro wants to merge 1 commit into
base: main
Choose a base branch
from
+6 −3
Open

Document sandbox limits #1081

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions docs/configuration/actions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,8 +24,11 @@ bash -c "my fancy $command | grep success"
> It's important to quote the content of the `-c` option so shell interprets it
> correctly as a single option input.
All actions are also executed inside Packit Service. The service
creates a new sandbox environment where the command is run.
SRPM creation actions run in Copr while release syncing actions are executed
in a sandbox environment inside Packit Service. This environment has limited resources.
Your actions shouldn't consume more than 768MiB of memory and use more than 3GiB of disk space.
Be aware that cloned upstream and dist-git repos also count towards this limit.
It is recommended to place any temporary artifacts in a subdirectory of `/tmp`, as there is no limit.
Copy link
Member Author

@nforro nforro Jan 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a bit unsure about this, because the limited volume with cloned git repos is mounted at /tmp/sandcastle, which is technically also a subdirectory of /tmp.

Copy link
Member

@majamassarini majamassarini Jan 9, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure either.
oc describe limitrange -n packit--prod-sandbox
Shows that the default limit for the storage in packit--prod-sandbox is 2Gi, I expect it to apply outside the mount point of our volume claim.

Copy link
Member Author

@nforro nforro Jan 9, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure either. oc describe limitrange -n packit--prod-sandbox Shows that the default limit for the storage in packit--prod-sandbox is 2Gi, I expect it to apply outside the mount point of our volume claim.

That's not what I'm unsure about, there is no limit apart from node physical disk size. I suppose you are talking about the 2GiB container image size limit, which is completely irrelevant here.

Copy link
Member

@lbarcziova lbarcziova Jan 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am unsure about this too, in the cluster I can see limits.ephemeral-storage set to 10Gi, although I am not sure how exactly (if) this is being enforced, as I don't see per-pod limits for the ephermal storage. I would rather omit this part and not recommend this.

Copy link
Member Author

@nforro nforro Jan 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have to admit I didn't try to dig deeper, I just did multiple practical tests creating large files and monitoring reported free space and I haven't found a node where there would be less than 50GiB of available space outside of /tmp/sandcastle. Even if there was 10GiB limit, it's still more than 3GiB and it would solve the issue for llvm-test-suite.

But if you prefer to omit this and rather increase the PVC in case more users report struggling to fit into 3GiB, it's fine by me.


Actions have a default behaviour which you can override, hooks don't have any -
hooks are a way for you to perform operations following a certain packit event,
Expand Down Expand Up @@ -77,7 +80,7 @@ These apply to `propose-downstream` command/job and `pull-from-upstream` job.

### Creating SRPM

These apply to the `srpm` command and building in COPR.
These apply to the `srpm` command and building in Copr.

| | name | working directory | when run | description |
|--------|-----------------------|-------------------|-----------------------------------------------------------------------|------------------------------------------------------|
Expand Down
Loading