You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- **Build timeouts** - Adjust build timeout settings based on workload requirements
349
349
350
-
For additional configuration options and advanced features, see [Configure Wave](../configure-wave.md).
350
+
For additional configuration options and advanced features, see [Configuring Wave](../configure-wave.md).
351
+
352
+
## Bottlerocket support
353
+
354
+
Buildkit requires user namespaces. However, Bottlerocket sets `user.max_user_namespaces=0` by default for security.
355
+
356
+
To use Buildkit with Bottlerocket, enable user namespaces for container builds by setting `user.max_user_namespaces=N` on your host nodes, where `N` is a positive integer. Use a sufficiently high value (e.g., `62000`) to avoid build failures. Values that are too low (e.g., `10`) will limit concurrent build capacity and may cause build failures.
357
+
358
+
You can configure this setting in two ways:
359
+
360
+
#### Recommended: Node startup configuration
361
+
362
+
Configure the user namespace setting in your node group's startup script or user data. This approach applies the configuration at boot time and doesn't require privileged containers in your cluster.
363
+
364
+
#### Alternative: DaemonSet
365
+
366
+
If you can't control the node configuration directly, use DaemonSet. This approach requires running a privileged container. We recommend you deploy it only on wave-build nodes and use a dedicated namespace for isolation.
0 commit comments