3 ms·
I did this once for an experimental project and found it really difficult to keep the version of gVisor I was using up to date, since it seems like the API is e
by dave78 2y ago
I did this once for an experimental project and found it really difficult to keep the version of gVisor I was using up to date, since it seems like the API is extremely volatile. Anyone else had this experience? If so, is there some way around it that I don't know? Or did I just try it at a bad point in the development timeline?
- ignoramous 2y agoThe API is indeed prone to change without notice, but it isn't anything terribly unmanageable. > really difficult to keep the version of gVisor I was using up to date For our project, we update gvisor whenever Tailscale does.
- iangudger 2y agoIt could be that you happened to find a period of rapid change, but it is also possible that you ran into the issue that raggi mentioned in the sibling comment.
- mort96 2y agoThat's just how Google operates in my experience... Avoid Google libraries unless absolutely necessary, and if you do adopt Google libraries, be prepared to either be forever multiple years out of date or spend significant resources on keeping it up to date.
- dgb23 2y agoPlus those libraries are often very hard to read and understand. Maybe I'm just dense though.