root
/
buildah
mirror of https://github.com/containers/buildah.git
1
0
Fork 0
Code Issues Actions 3 Packages Projects Releases Wiki Activity
buildah/docs/buildah-source-pull.1.md

29 lines
952 B
Markdown
Raw Permalink Normal View History

Install new manpages to correct sections Signed-off-by: Reinhard Tartler <siretart@tauware.de>
2021-08-30 03:28:53 +08:00
# buildah-source-pull "1" "March 2021" "buildah"
buildah source - create and manage source images Add new `buildah source {create,add,push,pull}` commands. All commands are marked as experimental. None of it is meant to be officially supported at the time of writing. All code resides in `internal/source` and is hence not visible to external consumers of Buildah; just to be on the safe side. A source container or source image is an OCI artifact, that is an OCI image with custom config (media type). There is a longer history behind source images which are intended to ship the source artifacts of an ordinary "executable" container image. Until now, source images at Red Hat are built with github.com/containers/BuildSourceImage. We had a growing desire (and always the long-term plan) to eventually replace BuildSurceImage with something else, in this case Buildah. This commit adds the initial base functionality along with tests to make sure we're not regressing. The new commands do the following: * `create` - creates an empty and initialized source image * `add` - tar up a local path and add it as a layer to the souce image * `push/pull` - intentionally separate commands from `buildah push/pull` to allow for an easier usage and prevent the implementations from undesired (future) interference Further note: also vendor in c/image@master which ships a required fix. Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
2021-03-22 20:02:39 +08:00
## NAME
buildah\-source\-pull - Pull a source image from a registry to a specified path
## SYNOPSIS
**buildah source pull** [*options*] *registry* *path*
## DESCRIPTION
Pull a source image from a registry to a specified path. The pull operation
[CI:DOCS] Fix typos and improve language Signed-off-by: Erik Sjölund <erik.sjolund@gmail.com>
2022-01-26 04:55:55 +08:00
will fail if the image does not comply with a source-image OCI artifact.
buildah source - create and manage source images Add new `buildah source {create,add,push,pull}` commands. All commands are marked as experimental. None of it is meant to be officially supported at the time of writing. All code resides in `internal/source` and is hence not visible to external consumers of Buildah; just to be on the safe side. A source container or source image is an OCI artifact, that is an OCI image with custom config (media type). There is a longer history behind source images which are intended to ship the source artifacts of an ordinary "executable" container image. Until now, source images at Red Hat are built with github.com/containers/BuildSourceImage. We had a growing desire (and always the long-term plan) to eventually replace BuildSurceImage with something else, in this case Buildah. This commit adds the initial base functionality along with tests to make sure we're not regressing. The new commands do the following: * `create` - creates an empty and initialized source image * `add` - tar up a local path and add it as a layer to the souce image * `push/pull` - intentionally separate commands from `buildah push/pull` to allow for an easier usage and prevent the implementations from undesired (future) interference Further note: also vendor in c/image@master which ships a required fix. Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
2021-03-22 20:02:39 +08:00
Note that the buildah-source command and all its subcommands are experimental
and may be subject to future changes.
## OPTIONS
**--creds** *creds*
The [username[:password]] to use to authenticate with the registry if required.
If one or both values are not supplied, a command line prompt will appear and the
value can be entered. The password is entered without echo.
**--tls-verify** *bool-value*
Require HTTPS and verification of certificates when talking to container
registries (defaults to true). TLS verification cannot be used when talking to
an insecure registry.