diff options
| author | Fabricio Voznika <fvoznika@google.com> | 2019-01-11 10:32:17 -0800 |
|---|---|---|
| committer | Shentubot <shentubot@google.com> | 2019-01-11 10:33:31 -0800 |
| commit | 864eac4a5baa80df0cee611ca8dd43e2910c5c49 (patch) | |
| tree | 7d588b0f7471d47a1128f7bb3c53580445b8ed03 | |
| parent | f8c8f241540fa79b47090ce4808c2c0cfbe44a12 (diff) | |
Update readme to say that 'kubectl cp' works
PiperOrigin-RevId: 228904169
Change-Id: I948f417d1336cb69c5733b142c53850507432fda
| -rw-r--r-- | README.md | 5 |
1 files changed, 4 insertions, 1 deletions
@@ -411,7 +411,7 @@ above. You're using an old version of Docker. Refer to the [Requirements](#requirements) section for the minimum version supported. -### I can’t see a file copied with `docker cp` or `kubectl cp`. +### I can’t see a file copied with `docker cp`. For performance reasons, gVisor caches directory contents, and therefore it may not realize a new file was copied to a given directory. To invalidate the cache @@ -420,6 +420,9 @@ contents again. This bug is tracked in [bug #4](https://github.com/google/gvisor/issues/4). +Note that `kubectl cp` works because it does the copy by exec'ing inside the +sandbox, and thus gVisor cache is aware of the new files and dirs. + ## Technical details We plan to release a full paper with technical details and will include it here |