forked from containers/podman
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove the ability to use [name:tag] in podman load command
Docker does not support this, and it is confusing what to do if the image has more then one tag. We are dropping support for this in podman 3.0 Fixes: containers#7387 Signed-off-by: Daniel J Walsh <[email protected]>
- Loading branch information
Showing
12 changed files
with
23 additions
and
113 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,13 +4,12 @@ | |
podman\-load - Load image(s) from a tar archive into container storage | ||
|
||
## SYNOPSIS | ||
**podman load** [*options*] [*name*[:*tag*]] | ||
**podman load** [*options*] | ||
|
||
**podman image load** [*options*] [*name*[:*tag*]] | ||
**podman image load** [*options*] | ||
|
||
## DESCRIPTION | ||
**podman load** loads an image from either an **oci-archive** or a **docker-archive** stored on the local machine into container storage. **podman load** reads from stdin by default or a file if the **input** option is set. | ||
You can also specify a name for the image if the archive is of single image and load will tag an additional image with the name:tag. | ||
**podman load** is used for loading from the archive generated by **podman save**, that includes the image parent layers. To load the archive of container's filesystem created by **podman export**, use **podman import**. | ||
|
||
The local client further supports loading an **oci-dir** or a **docker-dir** as created with **podman save** (1). | ||
|
@@ -23,7 +22,7 @@ Note: `:` is a restricted character and cannot be part of the file name. | |
|
||
**podman load [GLOBAL OPTIONS]** | ||
|
||
**podman load [OPTIONS] NAME[:TAG]** | ||
**podman load [OPTIONS]** | ||
|
||
## OPTIONS | ||
|
||
|
@@ -78,7 +77,7 @@ Loaded image: registry.fedoraproject.org/fedora:latest | |
``` | ||
|
||
## SEE ALSO | ||
podman(1), podman-save(1), podman-tag(1) | ||
podman(1), podman-save(1) | ||
|
||
## HISTORY | ||
July 2017, Originally compiled by Urvashi Mohnani <[email protected]> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters