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
When git credentials are added to a workspace (doc), the credentials file is necessarily mounted read-only to the workspace containers.
This causes git operations, both in the running workspace and in the project-clone init container, to log
fatal: unable to get credential storage lock in 1000 ms: Read-only file system
This message does not prevent the action from succeeding (i.e. the clone/fetch/push succeeds) but the message is confusing and suggests an unexpected error.
How To Reproduce
Configure git credentials via personal access token as documented
Description
When git credentials are added to a workspace (doc), the credentials file is necessarily mounted read-only to the workspace containers.
This causes git operations, both in the running workspace and in the project-clone init container, to log
This message does not prevent the action from succeeding (i.e. the clone/fetch/push succeeds) but the message is confusing and suggests an unexpected error.
How To Reproduce
git fetch
within the cloned project, note error printed as above.Expected behavior
We should find a way of either ignoring or suppressing this error.
One approach would be to
However, this approach would prevent on-cluster updates to the git credentials from automatically propagating to the workspace, which is a requirement (see: Update how personal access token git credentials are mounted into workspaces #915)
Additional context
The text was updated successfully, but these errors were encountered: