.nh
.TH OCI-IMAGE-TOOL-CREATE(1) OCI Image Tool User Manuals
OCI Community
JULY 2016

.SH NAME
.PP
oci-image-tool create - Create an OCI runtime bundle


.SH SYNOPSIS
.PP
\fBoci-image-tool create\fP [src] [dest] [OPTIONS]


.SH DESCRIPTION
.PP
\fB\fCoci-image-tool create\fR validates an application/vnd.oci.image.manifest.v1+json and unpacks its layered filesystem to \fB\fCdest/rootfs\fR, although the target directory is configurable with \fB\fC--rootfs\fR\&. See \fBoci-image-tool unpack\fP(1) for more details on this process.

.PP
Also translates the referenced config from application/vnd.oci.image.config.v1+json to a
runtime-spec-compatible \fB\fCdest/config.json\fR\&.


.SH OPTIONS
.PP
\fB--help\fP
  Print usage statement

.PP
\fB--ref\fP=[]
  Specify the search criteria for the validated reference, format is A=B.
  Reference should point to a manifest or index.
  e.g. --ref name=v1.0 --ref platform.os=latest
  Only support \fB\fCname\fR, \fB\fCplatform.os\fR and \fB\fCdigest\fR three cases.

.PP
\fB--rootfs\fP=""
  A directory representing the root filesystem of the container in the OCI runtime bundle. It is strongly recommended to keep the default value. (default "rootfs")

.PP
\fB--type\fP=""
  Type of the file to unpack. If unset, oci-image-tool will try to auto-detect the type. One of "imageLayout,image,imageZip"

.PP
\fB--platform\fP=""
  Specify the os and architecture of the manifest, format is OS:Architecture.
  e.g. --platform linux:amd64
  Only applicable if reftype is index.


.SH EXAMPLES
.PP
.RS

.nf
$ skopeo copy docker://busybox oci:busybox-oci:latest
$ mkdir busybox-bundle
$ oci-image-tool create --ref name=latest busybox-oci busybox-bundle
$ cd busybox-bundle && sudo runc run busybox
[...]

.fi
.RE


.SH SEE ALSO
.PP
\fBrunc\fP(1), \fBskopeo\fP(1)


.SH HISTORY
.PP
Sept 2016, Originally compiled by Antonio Murdaca (runcom at redhat dot com)