Skip to content

Conversation

@giordano
Copy link
Member

ubuntu-slim is a new runner type for running short-lived (max 15 minutes) non-expensive tasks like linting, labelling, and such.

@giordano giordano added the ci Continuous integration label Jan 24, 2026
Comment on lines 11 to 16
runs-on: ubuntu-latest
runs-on: ubuntu-slim
timeout-minutes: 2
steps:
- uses: yogevbd/enforce-label-action@a3c219da6b8fa73f6ba62b68ff09c469b3a1c024 # 2.2.2
Copy link
Member Author

Choose a reason for hiding this comment

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

Uhm, this fails because yogevbd/enforce-label-action needs to build a Docker container, but ubuntu-slim itself runs inside a container, this is probably a nested container problem. Ok, will revert this one (but also, the upstream workflow looks quite inefficient...)

The workflow needs to build a Docker container, which doesn't seem to be
possible on a `ubuntu-slim` runner.
@DilumAluthge
Copy link
Member

In theory it sounds fine, but are these containers running on the same VM as other customers? How is that secure?

@DilumAluthge
Copy link
Member

In theory it sounds fine, but are these containers running on the same VM as other customers? How is that secure?

Are they doing this, maybe?

@giordano
Copy link
Member Author

Quoting from the link I shared above:

Each container provides hypervisor level 2 isolation, and the container is automatically decommissioned when a job is completed.

@DilumAluthge
Copy link
Member

Each container provides hypervisor level 2 isolation

Yeah, my question is more along the lines of: how exactly are they doing that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci Continuous integration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants