diff options
| author | Nalin Dahyabhai <nalin@redhat.com> | 2021-09-07 14:56:09 -0400 |
|---|---|---|
| committer | Nalin Dahyabhai <nalin@redhat.com> | 2021-09-07 15:29:33 -0400 |
| commit | 748c2700b4d839a43be6061ad3bedc3e2f08ab3a (patch) | |
| tree | 87a465d838ae70e0a36fdefd664b5f5dba2f0327 /pkg/machine | |
| parent | 536f23c0b78dd8feafee4e40b743988dbb03bfa2 (diff) | |
| download | podman-748c2700b4d839a43be6061ad3bedc3e2f08ab3a.tar.gz podman-748c2700b4d839a43be6061ad3bedc3e2f08ab3a.tar.bz2 podman-748c2700b4d839a43be6061ad3bedc3e2f08ab3a.zip | |
pkg/bindings/images.nTar(): set ownership of build context to 0:0
When attempting to run remote builds, users with UID/GID values that
were high enough that they wouldn't be mapped into their default user
namespace configurations would see their builds fail when the server
attempted to extract the build contexts that they supplied, and failed
to set ownership of the build context content to the UID/GID that were
originally assigned to them.
When archiving the build context at the client, set ownership of
everything to 0:0, which we know is always mapped. Both ADD and COPY
require that we set the ownership of newly-added content to 0:0 (unless
the --chown flag is used), so throwing away the original ownership
information doesn't hurt, anyway. As usual, tarballs that we extract
as part of ADD aren't going to be affected.
Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
Diffstat (limited to 'pkg/machine')
0 files changed, 0 insertions, 0 deletions