mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-08-10 02:45:44 +00:00
748c2700b4
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> |
||
|---|---|---|
| .. | ||
| build.go | ||
| build_test.go | ||
| build_unix.go | ||
| build_windows.go | ||
| diff.go | ||
| images.go | ||
| pull.go | ||
| rm.go | ||
| types.go | ||
| types_diff_options.go | ||
| types_exists_options.go | ||
| types_export_options.go | ||
| types_get_options.go | ||
| types_history_options.go | ||
| types_import_options.go | ||
| types_list_options.go | ||
| types_load_options.go | ||
| types_prune_options.go | ||
| types_pull_options.go | ||
| types_push_options.go | ||
| types_remove_options.go | ||
| types_search_options.go | ||
| types_tag_options.go | ||
| types_tree_options.go | ||
| types_untag_options.go | ||