Skip to content

docs: add Bottlerocket section to rootless Podman #17987

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

Merged
merged 2 commits into from
May 22, 2025
Merged

docs: add Bottlerocket section to rootless Podman #17987

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b664cb2
docs: add Bottlerocket section to rootless Podman
krispage May 22, 2025
1041116
changes from feedback
ericpaulsen May 22, 2025
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
39 changes: 39 additions & 0 deletions docs/admin/templates/extending-templates/docker-in-workspaces.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -266,6 +266,45 @@ Before using Podman, please review the following documentation:
> For more information around the requirements of rootless podman pods, see:
> [How to run Podman inside of Kubernetes](https://www.redhat.com/sysadmin/podman-inside-kubernetes)

### Rootless Podman on Bottlerocket nodes

Rootless containers rely on Linux user-namespaces.
[Bottlerocket](https://github.com/bottlerocket-os/bottlerocket) disables them by default (`user.max_user_namespaces = 0`), so Podman commands will return an error until you raise the limit:

```output
cannot clone: Invalid argument
user namespaces are not enabled in /proc/sys/user/max_user_namespaces
```

1. Add a `user.max_user_namespaces` value to your Bottlerocket user data to use rootless Podman on the node:

```toml
[settings.kernel.sysctl]
"user.max_user_namespaces" = "65536"
```

1. Reboot the node.
1. Verify that the value is more than `0`:

```shell
sysctl -n user.max_user_namespaces
```

For Karpenter-managed Bottlerocket nodes, add the `user.max_user_namespaces` setting in your `EC2NodeClass`:

```yaml
apiVersion: karpenter.k8s.aws/v1
kind: EC2NodeClass
metadata:
name: bottlerocket-rootless
spec:
amiFamily: Bottlerocket # required for BR-style userData
# …
userData: |
[settings.kernel]
sysctl = { "user.max_user_namespaces" = "65536" }
```

## Privileged sidecar container

A
Expand Down
Loading