Repository navigation
docs: troubleshoot restricted deployment directories - #83
Merged
Merged
Conversation
1 of 3 tasks
timokoessler
approved these changes
Oct 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Deployments can fail when application-owned directories prevent the Agent from checking a bind mount source for symlinks. Add troubleshooting guidance covering the error, directory search permissions, and an explicit
DAC_READ_SEARCHoption for the Agent, including its broader read access and the container recreation step.The guide explains why symlink checks remain enabled and why allowing a privileged application bypass is unnecessary for this error.
Companion to OrcaCD/orca-cd#445; addresses OrcaCD/orca-cd#444.
Validation: type checks, lint, formatting, and production build (using
NODE_OPTIONS=--dns-result-order=ipv4firstfor local prerendering).