*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
#!/bin/bash
|
2019-09-05 21:10:39 +00:00
|
|
|
|
|
|
|
# This script builds a Source Image via "drivers" to collect source
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
|
|
|
|
export ABV_NAME="SrcImg"
|
|
|
|
# TODO maybe a flag for this?
|
|
|
|
export source_image_suffix="-source"
|
|
|
|
|
|
|
|
|
|
|
|
_usage() {
|
2019-09-05 21:10:39 +00:00
|
|
|
echo "Usage: $(basename $0) [-D] [-b <path>] [-c <path>] [-e <path>] [-r <path>] [-o <path>] [-i <image>] [-p <image>] [-l] [-d <drivers>]"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
echo ""
|
|
|
|
echo -e " -b <path>\tbase path for source image builds"
|
|
|
|
echo -e " -c <path>\tbuild context for the container image. Can be provided via CONTEXT_DIR env variable"
|
|
|
|
echo -e " -e <path>\textra src for the container image. Can be provided via EXTRA_SRC_DIR env variable"
|
2019-09-04 20:48:52 +00:00
|
|
|
echo -e " -r <path>\tdirectory of RPMS to add. Can be provided via RPM_DIR env variable"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
echo -e " -o <path>\toutput the OCI image to path. Can be provided via OUTPUT_DIR env variable"
|
|
|
|
echo -e " -d <drivers>\toutput the OCI image to path. Can be provided via OUTPUT_DIR env variable"
|
|
|
|
echo -e " -l\t\tlist the source drivers available"
|
2019-09-05 21:10:39 +00:00
|
|
|
echo -e " -i <image>\timage reference to fetch and inspect its rootfs"
|
|
|
|
echo -e " -p <image>\tpush source image to reference after build"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
echo -e " -D\t\tdebuging output. Can be set via DEBUG env variable"
|
2019-07-31 23:19:47 +00:00
|
|
|
exit 1
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
}
|
|
|
|
|
2019-07-12 18:44:41 +00:00
|
|
|
#
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
# sanity checks on startup
|
2019-07-15 19:07:51 +00:00
|
|
|
#
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
_init() {
|
|
|
|
set -o pipefail
|
|
|
|
|
|
|
|
# check for tools we depend on
|
2019-09-05 21:10:39 +00:00
|
|
|
for cmd in jq skopeo dnf file find tar stat date ; do
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
if [ -z "$(command -v ${cmd})" ] ; then
|
|
|
|
# TODO: maybe this could be individual checks so it can report
|
|
|
|
# where to find the tools
|
2019-09-05 21:10:39 +00:00
|
|
|
echo "ERROR: please install package to provide '${cmd}'"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
fi
|
|
|
|
done
|
|
|
|
}
|
|
|
|
|
|
|
|
_is_sourced() {
|
|
|
|
# https://unix.stackexchange.com/a/215279
|
|
|
|
# thanks @tianon
|
|
|
|
[ "${FUNCNAME[${#FUNCNAME[@]} - 1]}" == 'source' ]
|
|
|
|
}
|
|
|
|
|
|
|
|
# count $character $string
|
|
|
|
_count() {
|
|
|
|
#expr $(echo "${2}" | tr "${1}" '\n' | wc -l) - 1
|
|
|
|
c="${2//[^${1}]}"
|
|
|
|
echo -n ${#c}
|
|
|
|
}
|
|
|
|
|
|
|
|
# size of file in bytes
|
|
|
|
_size() {
|
|
|
|
local file="${1}"
|
|
|
|
stat -c "%s" "${file}" | tr -d '\n'
|
|
|
|
}
|
|
|
|
|
|
|
|
# date timestamp in RFC 3339, to the nanosecond
|
|
|
|
_date_ns() {
|
|
|
|
date --rfc-3339=ns | tr -d '\n'
|
|
|
|
}
|
|
|
|
|
|
|
|
# local `mktemp -d`
|
|
|
|
_mktemp_d() {
|
|
|
|
mktemp -d "${TMPDIR:-/tmp}/${ABV_NAME}.XXXXXX"
|
|
|
|
}
|
|
|
|
|
|
|
|
# local `mktemp`
|
|
|
|
_mktemp() {
|
|
|
|
mktemp "${TMPDIR:-/tmp}/${ABV_NAME}.XXXXXX"
|
|
|
|
}
|
|
|
|
|
|
|
|
# local rm -rf
|
|
|
|
_rm_rf() {
|
2019-09-04 20:48:52 +00:00
|
|
|
_debug "rm -rf $@"
|
2019-09-05 21:10:39 +00:00
|
|
|
rm -rf $@
|
|
|
|
}
|
|
|
|
|
|
|
|
# local mkdir -p
|
|
|
|
_mkdir_p() {
|
|
|
|
if [ -n "${DEBUG}" ] ; then
|
|
|
|
mkdir -vp $@
|
|
|
|
else
|
|
|
|
mkdir -p $@
|
|
|
|
fi
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
# local tar
|
|
|
|
_tar() {
|
|
|
|
if [ -n "${DEBUG}" ] ; then
|
|
|
|
tar -v $@
|
|
|
|
else
|
|
|
|
tar $@
|
|
|
|
fi
|
|
|
|
}
|
|
|
|
|
|
|
|
# output things, only when $DEBUG is set
|
2019-09-04 20:48:52 +00:00
|
|
|
_debug() {
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
if [ -n "${DEBUG}" ] ; then
|
|
|
|
echo "[${ABV_NAME}][DEBUG] ${@}"
|
|
|
|
fi
|
|
|
|
}
|
2019-07-12 18:44:41 +00:00
|
|
|
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
# general echo but with prefix
|
2019-09-04 20:48:52 +00:00
|
|
|
_info() {
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
echo "[${ABV_NAME}][INFO] ${@}"
|
|
|
|
}
|
|
|
|
|
2019-09-05 21:10:39 +00:00
|
|
|
_warn() {
|
|
|
|
echo "[${ABV_NAME}][WARN] ${@}" >&2
|
|
|
|
}
|
|
|
|
|
2019-09-04 20:48:52 +00:00
|
|
|
# general echo but with prefix
|
|
|
|
_error() {
|
|
|
|
echo "[${ABV_NAME}][ERROR] ${@}" >&2
|
|
|
|
exit 1
|
|
|
|
}
|
|
|
|
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
#
|
|
|
|
# parse the OCI image reference, accounting for:
|
|
|
|
# * transport name
|
|
|
|
# * presence or lack of transport port number
|
|
|
|
# * presence or lack of digest
|
|
|
|
# * presence or lack of image tag
|
|
|
|
#
|
|
|
|
|
|
|
|
#
|
|
|
|
# return the image reference's digest, if any
|
|
|
|
#
|
|
|
|
parse_img_digest() {
|
|
|
|
local ref="${1}"
|
|
|
|
local digest=""
|
|
|
|
if [ "$(_count '@' ${ref})" -gt 0 ] ; then
|
|
|
|
digest="${ref##*@}" # the digest after the "@"
|
2019-07-12 18:44:41 +00:00
|
|
|
fi
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
echo -n "${digest}"
|
|
|
|
}
|
|
|
|
|
|
|
|
#
|
|
|
|
# determine image base name (without tag or digest)
|
|
|
|
#
|
|
|
|
parse_img_base() {
|
|
|
|
local ref="${1%@*}" # just the portion before the digest "@"
|
|
|
|
local base="${ref}" default to the same
|
|
|
|
if [ "$(_count ':' $(echo ${ref} | tr '/' '\n' | tail -1 ))" -gt 0 ] ; then
|
|
|
|
# which means everything before it is the base image name, **including
|
|
|
|
# transport (which could have a port delineation), and even a URI
|
|
|
|
base="$(echo ${ref} | rev | cut -d : -f 2 | rev )"
|
|
|
|
fi
|
|
|
|
echo -n "${base}"
|
|
|
|
}
|
|
|
|
|
|
|
|
#
|
|
|
|
# determine, or guess, the image tag from the provided image reference
|
|
|
|
#
|
|
|
|
parse_img_tag() {
|
|
|
|
local ref="${1%@*}" # just the portion before the digest "@"
|
|
|
|
local tag="latest" # default tag
|
2019-09-05 21:10:39 +00:00
|
|
|
|
|
|
|
if [ -z "${ref}" ] ; then
|
|
|
|
echo -n "${tag}"
|
|
|
|
return 0
|
|
|
|
fi
|
|
|
|
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
if [ "$(_count ':' $(echo ${ref} | tr '/' '\n' | tail -1 ))" -gt 0 ] ; then
|
|
|
|
# if there are colons in the last segment after '/', then get that tag name
|
|
|
|
tag="$(echo ${ref} | tr '/' '\n' | tail -1 | cut -d : -f 2 )"
|
|
|
|
fi
|
|
|
|
echo -n "${tag}"
|
|
|
|
}
|
|
|
|
|
|
|
|
#
|
|
|
|
# an inline prefixer for containers/image tools
|
|
|
|
#
|
|
|
|
ref_prefix() {
|
|
|
|
local ref="${1}"
|
|
|
|
|
|
|
|
# get the supported prefixes of the current version of skopeo
|
|
|
|
IFS=", "
|
|
|
|
local pfxs=( $(skopeo copy --help | grep -A1 "Supported transports:" | grep -v "Supported transports") )
|
|
|
|
unset IFS
|
|
|
|
|
|
|
|
for pfx in ${pfxs[@]} ; do
|
|
|
|
if echo ${ref} | grep -q "^${pfx}:" ; then
|
|
|
|
# break when we match
|
|
|
|
echo ${ref}
|
|
|
|
return 0
|
|
|
|
fi
|
|
|
|
done
|
|
|
|
# else default
|
|
|
|
echo "docker://${ref}"
|
|
|
|
}
|
|
|
|
|
|
|
|
#
|
|
|
|
# an inline namer for the source image
|
|
|
|
# Initially this is a tagging convention (which if we try estesp/manifest-tool
|
|
|
|
# can be directly mapped into a manifest-list/image-index).
|
|
|
|
#
|
|
|
|
ref_src_img_tag() {
|
|
|
|
local ref="${1}"
|
|
|
|
echo -n "$(parse_img_tag ${ref})${source_image_suffix}"
|
|
|
|
}
|
|
|
|
|
|
|
|
#
|
|
|
|
# call out to registry for the image reference's digest checksum
|
|
|
|
#
|
|
|
|
fetch_img_digest() {
|
|
|
|
local ref="${1}"
|
|
|
|
## TODO: check for authfile, creds, and whether it's an insecure registry
|
|
|
|
local dgst=$(skopeo inspect "$(ref_prefix ${ref})" | jq .Digest | tr -d \")
|
|
|
|
local ret=$?
|
|
|
|
if [ $ret -ne 0 ] ; then
|
|
|
|
echo "ERROR: check the image reference: ${ref}" >&2
|
|
|
|
return $ret
|
|
|
|
fi
|
|
|
|
|
|
|
|
echo -n "${dgst}"
|
|
|
|
}
|
|
|
|
|
|
|
|
#
|
|
|
|
# pull down the image to an OCI layout
|
|
|
|
# arguments: image ref
|
|
|
|
# returns: path:tag to the OCI layout
|
|
|
|
#
|
|
|
|
# any commands should only output to stderr, so that the caller can receive the
|
|
|
|
# path reference to the OCI layout.
|
|
|
|
#
|
|
|
|
fetch_img() {
|
|
|
|
local ref="${1}"
|
|
|
|
local dst="${2}"
|
|
|
|
|
2019-09-05 21:10:39 +00:00
|
|
|
_mkdir_p "${dst}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
|
|
|
|
local base="$(parse_img_base ${ref})"
|
|
|
|
local tag="$(parse_img_tag ${ref})"
|
|
|
|
local dgst="$(parse_img_digest ${ref})"
|
|
|
|
local from=""
|
|
|
|
# skopeo currently only support _either_ tag _or_ digest, so we'll be specific.
|
|
|
|
if [ -n "${dgst}" ] ; then
|
|
|
|
from="$(ref_prefix ${base})@${dgst}"
|
|
|
|
else
|
|
|
|
from="$(ref_prefix ${base}):${tag}"
|
|
|
|
fi
|
|
|
|
|
|
|
|
## TODO: check for authfile, creds, and whether it's an insecure registry
|
|
|
|
## destination name must have the image tag included (umoci expects it)
|
|
|
|
skopeo \
|
|
|
|
copy \
|
|
|
|
"${from}" \
|
|
|
|
"oci:${dst}:${tag}" >&2
|
|
|
|
echo -n "${dst}:${tag}"
|
|
|
|
}
|
|
|
|
|
|
|
|
#
|
|
|
|
# upack_img <oci layout path> <unpack path>
|
|
|
|
#
|
|
|
|
unpack_img() {
|
|
|
|
local image_dir="${1}"
|
|
|
|
local unpack_dir="${2}"
|
|
|
|
|
|
|
|
if [ -d "${unpack_dir}" ] ; then
|
|
|
|
_rm_rf "${unpack_dir}"
|
|
|
|
fi
|
|
|
|
|
|
|
|
# TODO perhaps if uid == 0 and podman is present then we can try it?
|
|
|
|
if [ -z "$(command -v umoci)" ] ; then
|
|
|
|
# can be done as non-root (even in a non-root container)
|
|
|
|
unpack_img_umoci "${image_dir}" "${unpack_dir}"
|
|
|
|
else
|
|
|
|
# can be done as non-root (even in a non-root container)
|
|
|
|
unpack_img_bash "${image_dir}" "${unpack_dir}"
|
|
|
|
fi
|
|
|
|
}
|
|
|
|
|
|
|
|
#
|
|
|
|
# unpack an image layout using only jq and bash
|
|
|
|
#
|
|
|
|
unpack_img_bash() {
|
|
|
|
local image_dir="${1}"
|
|
|
|
local unpack_dir="${2}"
|
|
|
|
|
2019-09-05 21:10:39 +00:00
|
|
|
# for compat with umoci (which wants the image tag as well)
|
|
|
|
if echo "${image_dir}" | grep -q ":" ; then
|
|
|
|
image_dir="${image_dir%:*}"
|
|
|
|
fi
|
|
|
|
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
local mnfst_dgst="$(cat "${image_dir}"/index.json | jq '.manifests[0].digest' | tr -d \" )"
|
|
|
|
|
|
|
|
# Since we're landing the reference as an OCI layout, this mediaType is fairly predictable
|
|
|
|
# TODO don't always assume +gzip
|
|
|
|
layer_dgsts="$(cat ${image_dir}/blobs/${mnfst_dgst/:/\/} | \
|
|
|
|
jq '.layers[] | select(.mediaType == "application/vnd.oci.image.layer.v1.tar+gzip") | .digest' | tr -d \")"
|
|
|
|
|
2019-09-05 21:10:39 +00:00
|
|
|
_mkdir_p "${unpack_dir}/rootfs"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
for dgst in ${layer_dgsts} ; do
|
|
|
|
path="${image_dir}/blobs/${dgst/:/\/}"
|
2019-09-05 21:10:39 +00:00
|
|
|
tmp_file=$(_mktemp)
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
zcat "${path}" | _tar -t > $tmp_file # TODO cleanup these files
|
|
|
|
|
|
|
|
# look for '.wh.' entries. They must be removed from the rootfs
|
|
|
|
# _before_ extracting the archive, then the .wh. entries themselves
|
|
|
|
# need to not remain afterwards
|
|
|
|
grep '\.wh\.' "${tmp_file}" | while read line ; do
|
|
|
|
# if `some/path/.wh.foo` then `rm -rf `${unpack_dir}/some/path/foo`
|
|
|
|
# if `some/path/.wh..wh..opq` then `rm -rf `${unpack_dir}/some/path/*`
|
|
|
|
if [ "$(basename ${line})" == ".wh..wh..opq" ] ; then
|
2019-09-05 21:10:39 +00:00
|
|
|
_rm_rf "${unpack_dir}/rootfs/$(dirname ${line})/*"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
elif basename "${line}" | grep -qe '^\.wh\.' ; then
|
|
|
|
name=$(basename "${line}" | sed -e 's/^\.wh\.//')
|
2019-09-05 21:10:39 +00:00
|
|
|
_rm_rf "${unpack_dir}/rootfs/$(dirname ${line})/${name}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
fi
|
|
|
|
done
|
|
|
|
|
2019-09-04 20:48:52 +00:00
|
|
|
_info "[unpacking] layer ${dgst}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
# unpack layer to rootfs (without whiteouts)
|
2019-09-05 21:10:39 +00:00
|
|
|
zcat "${path}" | _tar --restrict --no-xattr --no-acls --no-selinux --exclude='*.wh.*' -x -C "${unpack_dir}/rootfs"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
|
|
|
|
# some of the directories get unpacked as 0555, so removing them gives an EPERM
|
|
|
|
find "${unpack_dir}" -type d -exec chmod 0755 "{}" \;
|
|
|
|
done
|
|
|
|
}
|
|
|
|
|
|
|
|
#
|
|
|
|
# unpack using umoci
|
|
|
|
#
|
|
|
|
unpack_img_umoci() {
|
|
|
|
local image_dir="${1}"
|
|
|
|
local unpack_dir="${2}"
|
|
|
|
|
2019-09-04 20:48:52 +00:00
|
|
|
_debug "unpackging with umoci"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
# always assume we're not root I reckon
|
|
|
|
umoci unpack --rootless --image "${image_dir}" "${unpack_dir}" >&2
|
|
|
|
}
|
|
|
|
|
|
|
|
# TODO this is not worked out yet
|
|
|
|
push_img() {
|
|
|
|
local ref="${1}"
|
|
|
|
local path="${2}"
|
|
|
|
|
|
|
|
## TODO: check for authfile, creds, and whether it's an insecure registry
|
|
|
|
skopeo copy "oci:${path}:$(ref_src_img_tag ${ref})" "$(ref_prefix ${ref})"
|
|
|
|
}
|
|
|
|
|
|
|
|
#
|
|
|
|
# sets up a basic new OCI layout, for an image with the provided (or default 'latest') tag
|
|
|
|
#
|
|
|
|
layout_new() {
|
|
|
|
local out_dir="${1}"
|
|
|
|
local image_tag="${2:-latest}"
|
|
|
|
|
2019-09-05 21:10:39 +00:00
|
|
|
_mkdir_p "${out_dir}/blobs/sha256"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
echo '{"imageLayoutVersion":"1.0.0"}' > "${out_dir}/oci-layout"
|
|
|
|
local config='
|
|
|
|
{
|
|
|
|
"created": "'$(_date_ns)'",
|
|
|
|
"architecture": "amd64",
|
|
|
|
"os": "linux",
|
|
|
|
"config": {},
|
|
|
|
"rootfs": {
|
|
|
|
"type": "layers",
|
|
|
|
"diff_ids": []
|
|
|
|
}
|
|
|
|
}
|
|
|
|
'
|
2019-09-05 11:15:14 +00:00
|
|
|
local config_sum=$(echo "${config}" | jq -c | tr -d '\n' | sha256sum | awk '{ ORS=""; print $1 }')
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
echo "${config}" | jq -c | tr -d '\n' > "${out_dir}/blobs/sha256/${config_sum}"
|
|
|
|
|
|
|
|
local mnfst='
|
|
|
|
{
|
|
|
|
"schemaVersion": 2,
|
|
|
|
"config": {
|
|
|
|
"mediaType": "application/vnd.oci.image.config.v1+json",
|
|
|
|
"digest": "sha256:'"${config_sum}"'",
|
|
|
|
"size": '"$(_size ${out_dir}/blobs/sha256/${config_sum})"'
|
|
|
|
},
|
|
|
|
"layers": []
|
|
|
|
}
|
|
|
|
'
|
2019-09-05 11:15:14 +00:00
|
|
|
local mnfst_sum=$(echo "${mnfst}" | jq -c | tr -d '\n' | sha256sum | awk '{ ORS=""; print $1 }')
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
echo "${mnfst}" | jq -c | tr -d '\n' > "${out_dir}/blobs/sha256/${mnfst_sum}"
|
|
|
|
|
|
|
|
echo '
|
|
|
|
{
|
|
|
|
"schemaVersion": 2,
|
|
|
|
"manifests": [
|
|
|
|
{
|
|
|
|
"mediaType": "application/vnd.oci.image.manifest.v1+json",
|
|
|
|
"digest": "sha256:'"${mnfst_sum}"'",
|
|
|
|
"size": '"$(_size ${out_dir}/blobs/sha256/${mnfst_sum})"',
|
|
|
|
"annotations": {
|
|
|
|
"org.opencontainers.image.ref.name": "'"${image_tag}"'"
|
|
|
|
}
|
|
|
|
}
|
|
|
|
]
|
|
|
|
}
|
|
|
|
' | jq -c | tr -d '\n' > "${out_dir}/index.json"
|
|
|
|
}
|
|
|
|
|
|
|
|
# call this for every artifact, to insert it into an OCI layout
|
|
|
|
# args:
|
|
|
|
# * a path to the layout
|
|
|
|
# * a path to the artifact
|
|
|
|
# * the path inside the tar
|
2019-09-05 21:10:39 +00:00
|
|
|
# * json file to slurp in as annotations for this layer's OCI descriptor
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
# * tag used in the layout (default is 'latest')
|
|
|
|
#
|
|
|
|
layout_insert() {
|
|
|
|
local out_dir="${1}"
|
|
|
|
local artifact_path="${2}"
|
|
|
|
local tar_path="${3}"
|
2019-09-05 21:10:39 +00:00
|
|
|
local annotations_file="${4}"
|
|
|
|
local image_tag="${5:-latest}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
|
|
|
|
local mnfst_list="${out_dir}/index.json"
|
|
|
|
# get the digest to the manifest
|
|
|
|
test -f "${mnfst_list}" || return 1
|
2019-09-04 20:48:52 +00:00
|
|
|
local mnfst_dgst="$(cat ${mnfst_list} | jq --arg tag "${image_tag}" '
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
.manifests[]
|
2019-09-04 20:48:52 +00:00
|
|
|
| select(.annotations."org.opencontainers.image.ref.name" == $tag )
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
| .digest
|
|
|
|
' | tr -d \" | tr -d '\n' )"
|
|
|
|
local mnfst="${out_dir}/blobs/${mnfst_dgst/:/\/}"
|
|
|
|
test -f "${mnfst}" || return 1
|
|
|
|
|
|
|
|
# make tar of new object
|
|
|
|
local tmpdir="$(_mktemp_d)"
|
|
|
|
# TODO account for "artifact_path" being a directory?
|
|
|
|
local sum="$(sha256sum ${artifact_path} | awk '{ print $1 }')"
|
|
|
|
# making a blob store in the layer
|
2019-09-05 21:10:39 +00:00
|
|
|
_mkdir_p "${tmpdir}/blobs/sha256"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
cp "${artifact_path}" "${tmpdir}/blobs/sha256/${sum}"
|
|
|
|
if [ "$(basename ${tar_path})" == "$(basename ${artifact_path})" ] ; then
|
2019-09-05 21:10:39 +00:00
|
|
|
_mkdir_p "${tmpdir}/$(dirname ${tar_path})"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
# TODO this symlink need to be relative path, not to `/blobs/...`
|
|
|
|
ln -s "/blobs/sha256/${sum}" "${tmpdir}/${tar_path}"
|
|
|
|
else
|
2019-09-05 21:10:39 +00:00
|
|
|
_mkdir_p "${tmpdir}/${tar_path}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
# TODO this symlink need to be relative path, not to `/blobs/...`
|
|
|
|
ln -s "/blobs/sha256/${sum}" "${tmpdir}/${tar_path}/$(basename ${artifact_path})"
|
|
|
|
fi
|
|
|
|
local tmptar="$(_mktemp)"
|
|
|
|
|
|
|
|
# zero all the things for as consistent blobs as possible
|
|
|
|
_tar -C "${tmpdir}" --mtime=@0 --owner=0 --group=0 --mode='a+rw' --no-xattrs --no-selinux --no-acls -cf "${tmptar}" .
|
|
|
|
_rm_rf "${tmpdir}"
|
|
|
|
|
|
|
|
# checksum tar and move to blobs/sha256/$checksum
|
2019-09-05 11:15:14 +00:00
|
|
|
local tmptar_sum="$(sha256sum ${tmptar} | awk '{ ORS=""; print $1 }')"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
local tmptar_size="$(_size ${tmptar})"
|
|
|
|
mv "${tmptar}" "${out_dir}/blobs/sha256/${tmptar_sum}"
|
|
|
|
|
|
|
|
# find and read the prior config, mapped from the manifest
|
|
|
|
local config_sum="$(jq '.config.digest' "${mnfst}" | tr -d \")"
|
|
|
|
|
|
|
|
# use `jq` to append to prior config
|
|
|
|
local tmpconfig="$(_mktemp)"
|
|
|
|
cat "${out_dir}/blobs/${config_sum/:/\/}" | jq -c \
|
|
|
|
--arg date "$(_date_ns)" \
|
2019-09-04 20:48:52 +00:00
|
|
|
--arg tmptar_sum "sha256:${tmptar_sum}" \
|
|
|
|
--arg comment "#(nop) BuildSourceImage adding artifact: ${sum}" \
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
'
|
2019-09-04 20:48:52 +00:00
|
|
|
.created = $date
|
2019-09-05 21:10:39 +00:00
|
|
|
| .rootfs.diff_ids += [ $tmptar_sum ]
|
|
|
|
| .history += [
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
{
|
2019-09-04 20:48:52 +00:00
|
|
|
"created": $date,
|
|
|
|
"created_by": $comment
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
}
|
|
|
|
]
|
|
|
|
' > "${tmpconfig}"
|
|
|
|
_rm_rf "${out_dir}/blobs/${config_sum/:/\/}"
|
|
|
|
|
|
|
|
# rename the config blob to its new checksum
|
2019-09-05 11:15:14 +00:00
|
|
|
local tmpconfig_sum="$(sha256sum ${tmpconfig} | awk '{ ORS=""; print $1 }')"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
local tmpconfig_size="$(_size ${tmpconfig})"
|
|
|
|
mv "${tmpconfig}" "${out_dir}/blobs/sha256/${tmpconfig_sum}"
|
|
|
|
|
|
|
|
# append layers list in the manifest, and its new config mapping
|
|
|
|
local tmpmnfst="$(_mktemp)"
|
|
|
|
cat "${mnfst}" | jq -c \
|
2019-09-04 20:48:52 +00:00
|
|
|
--arg tmpconfig_sum "sha256:${tmpconfig_sum}" \
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
--arg tmpconfig_size "${tmpconfig_size}" \
|
2019-09-04 20:48:52 +00:00
|
|
|
--arg tmptar_sum "sha256:${tmptar_sum}" \
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
--arg tmptar_size "${tmptar_size}" \
|
|
|
|
--arg artifact "$(basename ${artifact_path})" \
|
2019-09-04 20:48:52 +00:00
|
|
|
--arg sum "sha256:${sum}" \
|
2019-09-05 21:10:39 +00:00
|
|
|
--slurpfile annotations_slup "${annotations_file}" \
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
'
|
2019-09-05 21:10:39 +00:00
|
|
|
.config.digest = $tmpconfig_sum
|
|
|
|
| .config.size = ($tmpconfig_size|tonumber)
|
|
|
|
| {
|
|
|
|
"com.redhat.layer.type": "source",
|
|
|
|
"com.redhat.layer.content": $artifact,
|
|
|
|
"com.redhat.layer.content.checksum": $sum
|
|
|
|
} + $annotations_slup[0] as $annotations_merge
|
|
|
|
| .layers += [
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
{
|
|
|
|
"mediaType": "application/vnd.oci.image.layer.v1.tar",
|
2019-09-05 21:10:39 +00:00
|
|
|
"size": ($tmptar_size|tonumber),
|
2019-09-04 20:48:52 +00:00
|
|
|
"digest": $tmptar_sum,
|
2019-09-05 21:10:39 +00:00
|
|
|
"annotations": $annotations_merge
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
}
|
|
|
|
]
|
|
|
|
' > "${tmpmnfst}"
|
2019-09-05 21:10:39 +00:00
|
|
|
ret=$?
|
|
|
|
if [ $ret -ne 0 ] ; then
|
|
|
|
return 1
|
|
|
|
fi
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
_rm_rf "${mnfst}"
|
|
|
|
|
|
|
|
# rename the manifest blob to its new checksum
|
2019-09-05 11:15:14 +00:00
|
|
|
local tmpmnfst_sum="$(sha256sum ${tmpmnfst} | awk '{ ORS=""; print $1 }')"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
local tmpmnfst_size="$(_size ${tmpmnfst})"
|
|
|
|
mv "${tmpmnfst}" "${out_dir}/blobs/sha256/${tmpmnfst_sum}"
|
|
|
|
|
|
|
|
# map the mnfst_list to the new mnfst checksum
|
|
|
|
local tmpmnfst_list="$(_mktemp)"
|
|
|
|
cat "${mnfst_list}" | jq -c \
|
|
|
|
--arg tag "${image_tag}" \
|
2019-09-05 21:10:39 +00:00
|
|
|
--arg tmpmnfst_sum "sha256:${tmpmnfst_sum}" \
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
--arg tmpmnfst_size "${tmpmnfst_size}" \
|
|
|
|
'
|
2019-09-05 21:10:39 +00:00
|
|
|
[(.manifests[] | select(.annotations."org.opencontainers.image.ref.name" != $tag) )] as $manifests_reduced
|
|
|
|
| [
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
{
|
|
|
|
"mediaType": "application/vnd.oci.image.manifest.v1+json",
|
2019-09-05 21:10:39 +00:00
|
|
|
"digest": $tmpmnfst_sum,
|
|
|
|
"size": ($tmpmnfst_size|tonumber),
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
"annotations": {
|
2019-09-05 21:10:39 +00:00
|
|
|
"com.redhat.image.type": "source",
|
|
|
|
"org.opencontainers.image.ref.name": $tag
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
}
|
|
|
|
}
|
2019-09-05 21:10:39 +00:00
|
|
|
] as $manifests_new
|
|
|
|
| .manifests = $manifests_reduced + $manifests_new
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
' > "${tmpmnfst_list}"
|
2019-09-05 21:10:39 +00:00
|
|
|
ret=$?
|
|
|
|
if [ $ret -ne 0 ] ; then
|
|
|
|
return 1
|
|
|
|
fi
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
mv "${tmpmnfst_list}" "${mnfst_list}"
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
# Source Collection Drivers
|
|
|
|
#
|
|
|
|
# presently just bash functions. *notice* prefix the function name as `sourcedriver_`
|
|
|
|
# May become a ${ABV_NAME}/drivers.d/
|
|
|
|
#
|
|
|
|
# Arguments:
|
|
|
|
# * image ref
|
|
|
|
# * path to inspect
|
|
|
|
# * output path for source (specifc to this driver)
|
2019-09-05 21:10:39 +00:00
|
|
|
# * output path for JSON file of source's annotations
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
#
|
2019-09-05 21:10:39 +00:00
|
|
|
# The JSON of source annotations is the key to discovering the source artifact
|
|
|
|
# to be added and including rich metadata about that archive into the final
|
|
|
|
# image.
|
|
|
|
# The name of each JSON file is appending '.json' to the artifact's name. So if
|
|
|
|
# you have `foo-1.0.src.rpm` then there MUST be a corresponding
|
|
|
|
# `foo-1.0.src.rpm.json`.
|
|
|
|
# The data structure in this annotation is just a dict/hashmap, with key/val
|
|
|
|
# according to
|
|
|
|
# https://github.com/opencontainers/image-spec/blob/master/annotations.md
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
#
|
|
|
|
|
|
|
|
#
|
|
|
|
# driver to determine and fetch source rpms, based on the rootfs
|
|
|
|
#
|
|
|
|
sourcedriver_rpm_fetch() {
|
2019-09-04 20:48:52 +00:00
|
|
|
local self="${0#sourcedriver_*}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
local ref="${1}"
|
|
|
|
local rootfs="${2}"
|
|
|
|
local out_dir="${3}"
|
|
|
|
local manifest_dir="${4}"
|
|
|
|
|
|
|
|
# Get the RELEASEVER from the image
|
|
|
|
local release=$(rpm -q --queryformat "%{VERSION}\n" --root ${rootfs} -f /etc/os-release)
|
|
|
|
|
|
|
|
# From the rootfs of the works image, build out the src rpms to operate over
|
|
|
|
for srcrpm in $(rpm -qa --root ${rootfs} --queryformat '%{SOURCERPM}\n' | grep -v '^gpg-pubkey' | sort -u) ; do
|
2019-09-05 21:10:39 +00:00
|
|
|
if [ "${srcrpm}" == "(none)" ] ; then
|
|
|
|
continue
|
|
|
|
fi
|
|
|
|
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
local rpm=${srcrpm%*.src.rpm}
|
|
|
|
if [ ! -f "${out_dir}/${srcrpm}" ] ; then
|
2019-09-04 20:48:52 +00:00
|
|
|
_info "--> fetching ${srcrpm}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
dnf download \
|
|
|
|
--quiet \
|
|
|
|
--installroot "${rootfs}" \
|
|
|
|
--release "${release}" \
|
|
|
|
--destdir "${out_dir}" \
|
|
|
|
--source \
|
2019-09-05 21:10:39 +00:00
|
|
|
"${rpm}"
|
|
|
|
ret=$?
|
|
|
|
if [ $ret -ne 0 ] ; then
|
|
|
|
_warn "failed to fetch ${srcrpm}"
|
|
|
|
continue
|
|
|
|
fi
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
else
|
2019-09-04 20:48:52 +00:00
|
|
|
_info "--> using cached ${srcrpm}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
fi
|
|
|
|
|
|
|
|
# XXX one day, check and confirm with %{sourcepkgid}
|
|
|
|
# https://bugzilla.redhat.com/show_bug.cgi?id=1741715
|
|
|
|
#local rpm_sourcepkgid=$(rpm -q --root ${rootfs} --queryformat '%{sourcepkgid}' "${rpm}")
|
2019-09-05 21:10:39 +00:00
|
|
|
local srcrpm_buildtime=$(rpm -qp --qf '%{buildtime}' ${out_dir}/${srcrpm} )
|
|
|
|
local srcrpm_pkgid=$(rpm -qp --qf '%{pkgid}' ${out_dir}/${srcrpm} )
|
|
|
|
local srcrpm_name=$(rpm -qp --qf '%{name}' ${out_dir}/${srcrpm} )
|
|
|
|
local srcrpm_version=$(rpm -qp --qf '%{version}' ${out_dir}/${srcrpm} )
|
|
|
|
local srcrpm_epoch=$(rpm -qp --qf '%{epoch}' ${out_dir}/${srcrpm} )
|
|
|
|
local srcrpm_release=$(rpm -qp --qf '%{release}' ${out_dir}/${srcrpm} )
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
local mimetype="$(file --brief --mime-type ${out_dir}/${srcrpm})"
|
|
|
|
jq \
|
|
|
|
-n \
|
2019-09-05 21:10:39 +00:00
|
|
|
--arg filename "${srcrpm}" \
|
|
|
|
--arg name "${srcrpm_name}" \
|
|
|
|
--arg version "${srcrpm_version}" \
|
|
|
|
--arg epoch "${srcrpm_epoch}" \
|
|
|
|
--arg release "${srcrpm_release}" \
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
--arg buildtime "${srcrpm_buildtime}" \
|
|
|
|
--arg mimetype "${mimetype}" \
|
|
|
|
'
|
2019-09-04 20:48:52 +00:00
|
|
|
{
|
2019-09-05 21:10:39 +00:00
|
|
|
"source.artifact.filename": $filename,
|
2019-09-04 20:48:52 +00:00
|
|
|
"source.artifact.name": $name,
|
2019-09-05 21:10:39 +00:00
|
|
|
"source.artifact.version": $version,
|
|
|
|
"source.artifact.epoch": $epoch,
|
|
|
|
"source.artifact.release": $release,
|
2019-09-04 20:48:52 +00:00
|
|
|
"source.artifact.mimetype": $mimetype,
|
|
|
|
"source.artifact.buildtime": $buildtime
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
}
|
|
|
|
' \
|
2019-09-05 21:10:39 +00:00
|
|
|
> "${manifest_dir}/${srcrpm}.json"
|
2019-09-04 20:48:52 +00:00
|
|
|
ret=$?
|
|
|
|
if [ $ret -ne 0 ] ; then
|
|
|
|
return 1
|
|
|
|
fi
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
done
|
|
|
|
}
|
|
|
|
|
2019-09-04 20:48:52 +00:00
|
|
|
#
|
|
|
|
# driver to only package rpms from a provided rpm directory
|
2019-09-05 21:10:39 +00:00
|
|
|
# (koji use-case)
|
2019-09-04 20:48:52 +00:00
|
|
|
#
|
|
|
|
sourcedriver_rpm_dir() {
|
|
|
|
local self="${0#sourcedriver_*}"
|
|
|
|
local ref="${1}"
|
|
|
|
local rootfs="${2}"
|
|
|
|
local out_dir="${3}"
|
|
|
|
local manifest_dir="${4}"
|
|
|
|
|
|
|
|
if [ -n "${RPM_DIR}" ]; then
|
|
|
|
_debug "$self: writing to $out_dir and $manifest_dir"
|
2019-09-05 21:10:39 +00:00
|
|
|
find "${RPM_DIR}" -type f -name '*src.rpm' | while read srcrpm ; do
|
|
|
|
cp "${srcrpm}" "${out_dir}"
|
|
|
|
local srcrpm_buildtime=$(rpm -qp --qf '%{buildtime}' ${out_dir}/${srcrpm} )
|
|
|
|
local srcrpm_pkgid=$(rpm -qp --qf '%{pkgid}' ${out_dir}/${srcrpm} )
|
|
|
|
local srcrpm_name=$(rpm -qp --qf '%{name}' ${out_dir}/${srcrpm} )
|
|
|
|
local srcrpm_version=$(rpm -qp --qf '%{version}' ${out_dir}/${srcrpm} )
|
|
|
|
local srcrpm_epoch=$(rpm -qp --qf '%{epoch}' ${out_dir}/${srcrpm} )
|
|
|
|
local srcrpm_release=$(rpm -qp --qf '%{release}' ${out_dir}/${srcrpm} )
|
|
|
|
local mimetype="$(file --brief --mime-type ${out_dir}/${srcrpm})"
|
|
|
|
jq \
|
|
|
|
-n \
|
|
|
|
--arg filename "${srcrpm}" \
|
|
|
|
--arg name "${srcrpm_name}" \
|
|
|
|
--arg version "${srcrpm_version}" \
|
|
|
|
--arg epoch "${srcrpm_epoch}" \
|
|
|
|
--arg release "${srcrpm_release}" \
|
|
|
|
--arg buildtime "${srcrpm_buildtime}" \
|
|
|
|
--arg mimetype "${mimetype}" \
|
|
|
|
'
|
|
|
|
{
|
|
|
|
"source.artifact.filename": $filename,
|
|
|
|
"source.artifact.name": $name,
|
|
|
|
"source.artifact.version": $version,
|
|
|
|
"source.artifact.epoch": $version,
|
|
|
|
"source.artifact.release": $release,
|
|
|
|
"source.artifact.mimetype": $mimetype,
|
|
|
|
"source.artifact.buildtime": $buildtime
|
|
|
|
}
|
|
|
|
' \
|
|
|
|
> "${manifest_dir}/${srcrpm}.json"
|
|
|
|
ret=$?
|
|
|
|
if [ $ret -ne 0 ] ; then
|
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
done
|
2019-09-04 20:48:52 +00:00
|
|
|
fi
|
|
|
|
}
|
|
|
|
|
2019-07-12 18:44:41 +00:00
|
|
|
#
|
|
|
|
# If the caller specified a context directory,
|
|
|
|
#
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
# slightly special driver, as it has a flag/env passed in, that it uses
|
|
|
|
#
|
|
|
|
sourcedriver_context_dir() {
|
2019-09-04 20:48:52 +00:00
|
|
|
local self="${0#sourcedriver_*}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
local ref="${1}"
|
|
|
|
local rootfs="${2}"
|
|
|
|
local out_dir="${3}"
|
|
|
|
local manifest_dir="${4}"
|
|
|
|
|
2019-09-04 20:48:52 +00:00
|
|
|
if [ -n "${CONTEXT_DIR}" ]; then
|
|
|
|
_debug "$self: writing to $out_dir and $manifest_dir"
|
|
|
|
local tarname="context.tar"
|
|
|
|
_tar -C "${CONTEXT_DIR}" \
|
|
|
|
--mtime=@0 --owner=0 --group=0 --mode='a+rw' --no-xattrs --no-selinux --no-acls \
|
|
|
|
-cf "${out_dir}/${tarname}" .
|
|
|
|
local mimetype="$(file --brief --mime-type ${out_dir}/${tarname})"
|
|
|
|
local source_info="${manifest_dir}/${tarname}.json"
|
|
|
|
jq \
|
|
|
|
-n \
|
|
|
|
--arg name "${tarname}" \
|
|
|
|
--arg mimetype "${mimetype}" \
|
|
|
|
'
|
|
|
|
{
|
|
|
|
"source.artifact.name": $name,
|
|
|
|
"source.artifact.mimetype": $mimetype
|
|
|
|
}
|
|
|
|
' \
|
|
|
|
> "${source_info}"
|
|
|
|
ret=$?
|
|
|
|
if [ $ret -ne 0 ] ; then
|
|
|
|
return 1
|
|
|
|
fi
|
|
|
|
fi
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
}
|
2019-07-12 18:44:41 +00:00
|
|
|
|
|
|
|
#
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
# If the caller specified a extra directory
|
2019-07-12 18:44:41 +00:00
|
|
|
#
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
# slightly special driver, as it has a flag/env passed in, that it uses
|
|
|
|
#
|
|
|
|
sourcedriver_extra_src_dir() {
|
2019-09-04 20:48:52 +00:00
|
|
|
local self="${0#sourcedriver_*}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
local ref="${1}"
|
|
|
|
local rootfs="${2}"
|
|
|
|
local out_dir="${3}"
|
|
|
|
local manifest_dir="${4}"
|
|
|
|
|
|
|
|
if [ -n "${EXTRA_SRC_DIR}" ]; then
|
2019-09-04 20:48:52 +00:00
|
|
|
_debug "$self: writing to $out_dir and $manifest_dir"
|
|
|
|
local tarname="extra-src.tar"
|
|
|
|
_tar -C "${EXTRA_SRC_DIR}" \
|
|
|
|
--mtime=@0 --owner=0 --group=0 --mode='a+rw' --no-xattrs --no-selinux --no-acls \
|
|
|
|
-cf "${out_dir}/${tarname}" .
|
|
|
|
local mimetype="$(file --brief --mime-type ${out_dir}/${tarname})"
|
|
|
|
local source_info="${manifest_dir}/${tarname}.json"
|
|
|
|
jq \
|
|
|
|
-n \
|
|
|
|
--arg name "${tarname}" \
|
|
|
|
--arg mimetype "${mimetype}" \
|
|
|
|
'
|
|
|
|
{
|
|
|
|
"source.artifact.name": $name,
|
|
|
|
"source.artifact.mimetype": $mimetype
|
|
|
|
}
|
|
|
|
' \
|
|
|
|
> "${source_info}"
|
|
|
|
ret=$?
|
|
|
|
if [ $ret -ne 0 ] ; then
|
|
|
|
return 1
|
|
|
|
fi
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
fi
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
main() {
|
|
|
|
_init ${@}
|
|
|
|
|
|
|
|
local base_dir="$(pwd)/${ABV_NAME}"
|
|
|
|
# using the bash builtin to parse
|
2019-09-05 21:10:39 +00:00
|
|
|
while getopts ":hlDi:c:r:e:o:b:d:p:" opts; do
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
case "${opts}" in
|
|
|
|
b)
|
|
|
|
base_dir="${OPTARG}"
|
|
|
|
;;
|
|
|
|
c)
|
|
|
|
local context_dir=${OPTARG}
|
|
|
|
;;
|
|
|
|
e)
|
|
|
|
local extra_src_dir=${OPTARG}
|
|
|
|
;;
|
2019-09-05 21:10:39 +00:00
|
|
|
d)
|
|
|
|
local drivers=${OPTARG}
|
2019-09-04 20:48:52 +00:00
|
|
|
;;
|
2019-09-05 21:10:39 +00:00
|
|
|
h)
|
|
|
|
_usage
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
;;
|
2019-09-05 21:10:39 +00:00
|
|
|
i)
|
|
|
|
local inspect_image_ref=${OPTARG}
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
;;
|
|
|
|
l)
|
2019-09-05 21:10:39 +00:00
|
|
|
local list_drivers=1
|
|
|
|
;;
|
|
|
|
o)
|
|
|
|
local output_dir=${OPTARG}
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
;;
|
|
|
|
p)
|
2019-09-05 21:10:39 +00:00
|
|
|
local push_image_ref${OPTARG}
|
|
|
|
;;
|
|
|
|
r)
|
|
|
|
local rpm_dir=${OPTARG}
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
;;
|
|
|
|
D)
|
|
|
|
export DEBUG=1
|
|
|
|
;;
|
|
|
|
*)
|
|
|
|
_usage
|
|
|
|
;;
|
|
|
|
esac
|
|
|
|
done
|
|
|
|
shift $((OPTIND-1))
|
|
|
|
|
|
|
|
if [ -n "${list_drivers}" ] ; then
|
|
|
|
set | grep '^sourcedriver_.* () ' | tr -d ' ()'
|
|
|
|
exit 0
|
|
|
|
fi
|
|
|
|
|
2019-09-05 21:10:39 +00:00
|
|
|
# These three variables are slightly special, in that they're globals that
|
|
|
|
# specific drivers will expect.
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
export CONTEXT_DIR="${CONTEXT_DIR:-$context_dir}"
|
|
|
|
export EXTRA_SRC_DIR="${EXTRA_SRC_DIR:-$extra_src_dir}"
|
2019-09-04 20:48:52 +00:00
|
|
|
export RPM_DIR="${RPM_DIR:-$rpm_dir}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
|
|
|
|
local output_dir="${OUTPUT_DIR:-$output_dir}"
|
|
|
|
|
2019-09-05 21:10:39 +00:00
|
|
|
export TMPDIR="${base_dir}/tmp"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
if [ -d "${TMPDIR}" ] ; then
|
|
|
|
_rm_rf "${TMPDIR}"
|
|
|
|
fi
|
2019-09-05 21:10:39 +00:00
|
|
|
_mkdir_p "${TMPDIR}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
|
2019-09-05 21:10:39 +00:00
|
|
|
# setup rootfs to be inspected (if any)
|
|
|
|
local rootfs=""
|
|
|
|
local image_ref=""
|
|
|
|
local src_dir=""
|
|
|
|
local work_dir="${base_dir}/work"
|
|
|
|
if [ -n "${inspect_image_ref}" ] ; then
|
|
|
|
_debug "Image Reference provided: ${inspect_image_ref}"
|
|
|
|
_debug "Image Reference base: $(parse_img_base ${inspect_image_ref})"
|
|
|
|
_debug "Image Reference tag: $(parse_img_tag ${inspect_image_ref})"
|
|
|
|
|
|
|
|
inspect_image_digest="$(parse_img_digest ${inspect_image_ref})"
|
|
|
|
# determine missing digest before fetch, so that we fetch the precise image
|
|
|
|
# including its digest.
|
|
|
|
if [ -z "${inspect_image_digest}" ] ; then
|
|
|
|
inspect_image_digest="$(fetch_img_digest $(parse_img_base ${inspect_image_ref}):$(parse_img_tag ${inspect_image_ref}))"
|
|
|
|
fi
|
|
|
|
_debug "inspect_image_digest: ${inspect_image_digest}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
|
2019-09-05 21:10:39 +00:00
|
|
|
local img_layout=""
|
|
|
|
# if inspect and fetch image, then to an OCI layout dir
|
|
|
|
if [ ! -d "${work_dir}/layouts/${inspect_image_digest/:/\/}" ] ; then
|
|
|
|
# we'll store the image to a path based on its digest, that it can be reused
|
|
|
|
img_layout="$(fetch_img $(parse_img_base ${inspect_image_ref}):$(parse_img_tag ${inspect_image_ref})@${inspect_image_digest} ${work_dir}/layouts/${inspect_image_digest/:/\/} )"
|
|
|
|
else
|
|
|
|
img_layout="${work_dir}/layouts/${inspect_image_digest/:/\/}:$(parse_img_tag ${inspect_image_ref})"
|
|
|
|
fi
|
|
|
|
_debug "image layout: ${img_layout}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
|
2019-09-05 21:10:39 +00:00
|
|
|
# unpack or reuse fetched image
|
|
|
|
local unpack_dir="${work_dir}/unpacked/${inspect_image_digest/:/\/}"
|
|
|
|
if [ -d "${unpack_dir}" ] ; then
|
|
|
|
_rm_rf "${unpack_dir}"
|
|
|
|
fi
|
|
|
|
unpack_img ${img_layout} ${unpack_dir}
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
|
2019-09-05 21:10:39 +00:00
|
|
|
rootfs="${unpack_dir}/rootfs"
|
|
|
|
image_ref="$(parse_img_base ${inspect_image_ref}):$(parse_img_tag ${inspect_image_ref})@${inspect_image_digest}"
|
|
|
|
src_dir="${base_dir}/src/${inspect_image_digest/:/\/}"
|
|
|
|
work_dir="${base_dir}/work/${inspect_image_digest/:/\/}"
|
|
|
|
_info "inspecting image reference ${image_ref}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
else
|
2019-09-05 21:10:39 +00:00
|
|
|
# if we're not fething an image, then this is basically a nop
|
|
|
|
rootfs="$(_mktemp_d)"
|
|
|
|
image_ref="scratch"
|
|
|
|
src_dir="$(_mktemp_d)"
|
|
|
|
work_dir="$(_mktemp_d)"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
fi
|
2019-09-04 20:48:52 +00:00
|
|
|
_debug "image layout: ${img_layout}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
|
|
|
|
# setup rootfs, from that OCI layout
|
|
|
|
local unpack_dir="${work_dir}/unpacked/${IMAGE_DIGEST/:/\/}"
|
|
|
|
if [ ! -d "${unpack_dir}" ] ; then
|
|
|
|
unpack_img ${img_layout} ${unpack_dir}
|
|
|
|
fi
|
2019-09-04 20:48:52 +00:00
|
|
|
_debug "unpacked dir: ${unpack_dir}"
|
2019-09-05 21:10:39 +00:00
|
|
|
_debug "rootfs dir: ${rootfs}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
|
|
|
|
# clear prior driver's info about source to insert into Source Image
|
2019-09-05 21:10:39 +00:00
|
|
|
_rm_rf "${work_dir}/driver"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
|
|
|
|
if [ -n "${drivers}" ] ; then
|
|
|
|
# clean up the args passed by the caller ...
|
|
|
|
drivers="$(echo ${drivers} | tr ',' ' '| tr '\n' ' ')"
|
|
|
|
else
|
|
|
|
drivers="$(set | grep '^sourcedriver_.* () ' | tr -d ' ()' | tr '\n' ' ')"
|
|
|
|
fi
|
2019-09-05 21:10:39 +00:00
|
|
|
|
|
|
|
# Prep the OCI layout for the source image
|
|
|
|
local src_img_dir="$(_mktemp_d)"
|
|
|
|
local src_img_tag="latest-source" #XXX this tag needs to be a reference to the image built from
|
|
|
|
layout_new "${src_img_dir}" "${src_img_tag}"
|
|
|
|
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
# iterate on the drivers
|
|
|
|
#for driver in sourcedriver_rpm_fetch ; do
|
|
|
|
for driver in ${drivers} ; do
|
2019-09-04 20:48:52 +00:00
|
|
|
_info "calling $driver"
|
2019-09-05 21:10:39 +00:00
|
|
|
_mkdir_p "${src_dir}/${driver#sourcedriver_*}"
|
|
|
|
_mkdir_p "${work_dir}/driver/${driver#sourcedriver_*}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
$driver \
|
2019-09-05 21:10:39 +00:00
|
|
|
"${image_ref}" \
|
|
|
|
"${rootfs}" \
|
|
|
|
"${src_dir}/${driver#sourcedriver_*}" \
|
|
|
|
"${work_dir}/driver/${driver#sourcedriver_*}"
|
|
|
|
local ret=$?
|
|
|
|
if [ $ret -ne 0 ] ; then
|
2019-09-04 20:48:52 +00:00
|
|
|
_error "$driver failed"
|
|
|
|
fi
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
|
2019-09-05 21:10:39 +00:00
|
|
|
# walk the driver output to determine layers to be added
|
|
|
|
find "${work_dir}/driver/${driver#sourcedriver_*}" -type f -name '*.json' | while read src_json ; do
|
|
|
|
local src_name=$(basename "${src_json}" .json)
|
|
|
|
layout_insert \
|
|
|
|
"${src_img_dir}" \
|
|
|
|
"${src_dir}/${driver#sourcedriver_*}/${src_name}" \
|
|
|
|
"/${driver#sourcedriver_*}/${src_name}" \
|
|
|
|
"${src_json}" \
|
|
|
|
"${src_img_tag}"
|
|
|
|
ret=$?
|
|
|
|
if [ $ret -ne 0 ] ; then
|
|
|
|
# TODO probably just _error here to exit
|
|
|
|
_warn "failed to insert layout layer for ${src_name}"
|
|
|
|
fi
|
|
|
|
done
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
done
|
|
|
|
|
2019-09-05 21:10:39 +00:00
|
|
|
_info "packed 'oci:$src_img_dir:${src_img_tag}'"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
|
2019-09-05 21:10:39 +00:00
|
|
|
# TODO maybe look to a directory like /usr/libexec/BuildSourceImage/drivers/ for drop-ins to run
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
|
|
|
|
## if an output directory is provided then save a copy to it
|
|
|
|
if [ -n "${output_dir}" ] ; then
|
2019-09-05 21:10:39 +00:00
|
|
|
_mkdir_p "${output_dir}"
|
|
|
|
push_img "oci:$src_img_dir:${src_img_tag}" "oci:$output_dir:$(ref_src_img_tag $(parse_img_tag ${inspect_image_ref}))"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
fi
|
2019-07-12 18:44:41 +00:00
|
|
|
|
2019-09-05 21:10:39 +00:00
|
|
|
if [ -n "${push_image_ref}" ] ; then
|
|
|
|
# XXX may have to parse this reference to ensure it is valid, and that it has a `-source` tag
|
|
|
|
push_img "oci:$src_img_dir:${src_img_tag}" "${push_image_ref}"
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
fi
|
2019-08-14 15:15:46 +00:00
|
|
|
|
*: big rewrite
_(this is a WIP)_
for the requirements to not be so bound to RPM only, breaking collection
of sources out into "plugins". Currently not much more sophisticated
than just iterating through bash functions that expect 3 argugments.
rootfs of the inspectee; output path for the sources collected; manifest
path.
The idea for the manifest is still loose, but how best to follow up the
plugin which collected source, to then have the rich metadata available
to attach to the individual "layers" that are produced for each source
component.
for the requirement of most contrained non-root container running this
script as non-root, we'll switch away from buildah for now. This ought
to just be skopeo copy, unpacking, inspecting, json, and skopeo copy. No
mounting, no namespacing, etc.
for the sake of writing unit tests (i.e. `bats`), break the script into
a way that it can be sourced and run the functions individually. Only
act like the whole script when run directly.
If `umoci` is available it will get used for some functions (like
unpacking), but it is not required and will be attempted with jq and
bash otherwise.
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2019-08-19 21:35:25 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
# only exec main if this is being called (this way we can source and test the functions)
|
|
|
|
_is_sourced || main ${@}
|
2019-08-14 15:15:46 +00:00
|
|
|
|
|
|
|
# vim:set shiftwidth=4 softtabstop=4 expandtab:
|