[Windows] Encrypted file store stale lock should get auto-recovered
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
The issue does not name specific files or tests. Start by locating the encrypted file store and comparing its Windows lock handling with the Unix recovery strategy; investigate whether delete-on-close addresses stale locks. Done means a stale lock can be recovered on Windows without preventing later processes from using the store.
Written by the indexing model from the issue text.
Description
The current implementation inside the encrypted file store has an OS file lock to prevent multiple processes from writing to the store. If the lock does not get removed, it could cause UX headache for the user. A recovery strategy is in place on Unix systems, but this does not work on Windows.
There might be an option to mark the file as "delete upon close", which means the lock file wouldn't persist between processes, but it might solve stale locks. We should look into it.
- Dominant language
- Go
- Stars
- 92
- Forks
- 17
- Avg merge
- 9h 42m
- Merged PRs (30d)
- 24
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker/secrets-engine
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
docker/secrets-engine#665 ·
Maintainers usually reply within 1 day
-
Linux keychain dials a new D-Bus connection per operation, defeating per-entry access confirmationOpen
Difficulty 5/5 Over a week Newbie friendliness 42/100
docker/secrets-engine#648 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
docker/secrets-engine#584 · 1 comment · 2 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
docker/secrets-engine#551 · 2 comments · 3 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
docker/secrets-engine#534 · 16 comments · 4 reactions ·
Maintainers usually reply within 1 day
All issues in docker/secrets-engine
Similar issues
-
Remove CAAPFOpenkind/chore kind/cleanup needs-area
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
rancher/turtles#2848 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
priority: low 🌱 type: enhancement 💅🏼
Difficulty 2/5 Half a day Newbie friendliness 84/100
nebari-dev/llm-serving-pack#199 ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kedacore/keda#8225 · 1 comment ·
Maintainers usually reply within 1 day