exec updater errors when using non-root user
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Repro steps:
- Create a NodeJS project with live_update sync
- Follow best practices of using a non-root user, as described in https://github.com/nodejs/docker-node/blob/master/docs/BestPractices.md#non-root-user
tilt upwith microk8s and try to modify a file
Expected result:
Tilt should sync the file successfully
Actual result:
Tilt fails with cryptic errors
Branch with repro code:
https://github.com/windmilleng/nodejs-express-k8s/tree/nicks/user
Snapshot:
https://cloud.tilt.dev/snapshot/AdyPt-YLRPKSa_XuHBg=
(see the alert)
Thanks to Marlow in the #tilt k8s channel for reporting
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
Start by reproducing the failure with the linked nodejs-express-k8s branch, microk8s, and a non-root NodeJS user; inspect the alert's cryptic error from the exec updater. Done means live_update sync succeeds after modifying a file and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, nodejs
- Domain
- devtools, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100