Skip to content

[1.16] Add docs on DAPR_UNSAFE_SKIP_CONTAINER_UID_GID_CHECK env var #4832

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
wants to merge 1 commit into
base: v1.16
Choose a base branch
from
+20 −1
Open

[1.16] Add docs on DAPR_UNSAFE_SKIP_CONTAINER_UID_GID_CHECK env var #4832

Show file tree
Hide file tree
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: 9 additions & 0 deletions daprdocs/content/en/concepts/security-concept.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -198,6 +198,15 @@ Let's go over each of the security capabilities and describe how they are protec
7. Service B is deployed to namespace "B", which further isolates it from other services. Even if the service invocation API was enabled on it, it could not be called accidentally by being in the same namespace as Service A. Service B must explicitly set the Redis Host namespace in its component YAML file to call onto the "Redis" namespace, otherwise this call also fails.
8. The data in the Redis state store is encrypted at rest and can only be read using the correctly configured Dapr Redis state store component.

## Run as non-root
When running in Kubernetes, Dapr services will ensure each process is running as non-root.
This is done by checking the UID & GID of the process is `65532`, and fatal erroring if it is not what is expected.
If you must run a non-default UID & GID in Kubernetes, set the following env var to skip this check.

```bash
DAPR_UNSAFE_SKIP_CONTAINER_UID_GID_CHECK="true"
```

# Threat model

Threat modeling is a process by which:
Expand Down
12 changes: 11 additions & 1 deletion daprdocs/content/en/operations/hosting/kubernetes/kubernetes-production.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -343,10 +343,20 @@ By default, the Dapr sidecar injector injects a sidecar without any `seccompProf

Refer to [the Arguments and Annotations overview]({{% ref "arguments-annotations-overview.md" %}}) to set the appropriate `seccompProfile` on the sidecar container.

## Best Practices
## Run as non-root
When running in Kubernetes, Dapr services will ensure each process is running as non-root.
This is done by checking the UID & GID of the process is `65532`, and fatal erroring if it is not what is expected.
If you must run a non-default UID & GID in Kubernetes, set the following env var to skip this check.

```bash
DAPR_UNSAFE_SKIP_CONTAINER_UID_GID_CHECK="true"
```

## Best Practices

Watch this video for a deep dive into the best practices for running Dapr in production with Kubernetes.


{{< youtube id=_U9wJqq-H1g >}}

## Related links
Expand Down
Loading