Work around permissions errors when syncing/untarring files
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
from @MattHodge:
Was having this error when live syncing, which is just tar's awful error when it doesn't have permissions:
etc/fun-facts/pgbouncer.supervisor.conf
etc/fun-facts/pgbouncer.userlist.txt
tar: etc/fun-facts/pgbouncer.userlist.txt: Cannot open: File exists
tar: etc/fun-facts/seelog.xml: Cannot open: File exists
tar: etc/fun-facts/test.ini: Cannot open: File exists
etc/fun-facts/seelog.xml
etc/fun-facts/test.ini
usr/local/bin/fun-facts
tar: usr/local/bin/fun-facts: Cannot open: File exists
tar: Exiting with failure status due to previous errors
got unexpected error during build/deploy: command terminated with exit code 2
Our container runs under a particular user but files baked into the image are using a different one
Tilt should have a way to work around permissions when sync'ing / be able to untar files as a specific user. Maybe the user can provide an optional custom "untar command"?
Contributor 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.
Research direction
The issue names no files, tests, or entry point. Start by locating Tilt's live-sync and untar implementation, then read its existing tests and determine how permission failures are currently surfaced. Done should include a defined permissions workaround and tests covering syncing files owned by a different user.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100