Closed EronWright closed 1 month ago
TODO: add securityProfile
to stack spec, to allow the workspace's profile to be configured, or expose a whole workspaceTemplate
.
Update: https://github.com/pulumi/pulumi-kubernetes-operator/pull/669
A nonroot variant of the kitchen sink image will be available soon: https://github.com/pulumi/pulumi-docker-containers/pull/277
I believe the remaining work on the PKO side is to use the correct default based on the security profile:
pulumi/pulumi:latest-nonroot
pulumi/pulumi:latest
Also remove the files in hack/rootless
and remove the makefile target docker-rootless
.
The latest-nonroot
tag is now published https://hub.docker.com/r/pulumi/pulumi/tags
Cannot close issue:
resolution/
Please fix these problems and try again.
Resolved by #693, #692 and https://github.com/pulumi/pulumi-docker-containers/pull/277.
For the pu/pu image to support non-root execution (a security best practice, and supported by PKOv2), we need to add a local user to the image.
Ideally we wouldn't have separate "nonroot" images (see the "distroless" images). Otherwise the defaulting logic would be more tricky.
One possibility is to add the local user as shown below but avoid using the
USER
instruction. I think that's sufficient for purposes of PKOv2, because the pod can apply a security context. TheUSER
instruction seems to set the default, which might be considered a breaking change for existing users of the pu/pu image.Here's an example of the Dockerfile commands:
And an example of the pod security context: