I switched to using a update-content.sh script, which is run at an earlier stage in the container setup process. This runs the direnv allow command before the VS Code extensions are loaded, preventing a warning about the workspace directory not being allowed.
I switched to using a
update-content.shscript, which is run at an earlier stage in the container setup process. This runs thedirenv allowcommand before the VS Code extensions are loaded, preventing a warning about the workspace directory not being allowed.