buildah-source-pull(1)

💅 buildah-source-pull — from the General Commands Manual besties ✨

🦋 NAME

buildah-source-pull — pull a source image from a registry and drop it at a path you pick, no cap

🌸 SYNOPSIS

buildah source pull [options] registry path

💖 DESCRIPTION

Okay so bestie, listen. You've got a source image chillin' in a registry somewhere, and you want it here, at a path you choose. That's literally the whole vibe of this command. Pull it, land it, done. Slay. 💅

But — and this is the important part — the pull operation is gonna fail if the image doesn't comply with a source-image OCI artifact. It's giving strict. It's giving standards. It will not be doing charity for random non-conforming images, periodt. 🙈

⚠️ Heads up: the buildah-source command and all of its subcommands are experimental and may be subject to future changes. So don't get too attached to the current behaviour, okay? It's in its main character era and still evolving. 🌈

✨ OPTIONS ✨

• --creds creds — the [username[:password]] you use to authenticate with the registry, if it's asking for it. If one or both of those values aren't supplied, a command line prompt pops up and you can enter the value right there. And the password? Entered without echo, so nobody's peeking, very demure, very private. 🎀
• --quiet, -q — suppresses the progress output while pulling a source image. Basically "bestie I don't need the play-by-play, just do it." Quiet luxury energy. 🤫
• --tls-verify bool-value — require HTTPS and verification of certificates when talking to container registries (defaults to true). Note that TLS verification cannot be used when talking to an insecure registry. It's giving secure or nothing. 🔥

That's the whole page, babe — every flag, every value, every default, nothing skipped, because we don't gatekeep around here. 🫶

This page came to you from buildah, dated March 2021, and it's the buildah-source-pull(1) manual page. 💖 Stay iconic, read your manpages, and remember: verification on, echo off. ✨🎀🦋