BUILDBOX-RUN-OCI(1)
π BUILDBOX-RUN-OCI π
okay so bestie, welcome to buildbox-run-oci, which lives in section 1 of the manual (that's the "type it in your terminal, queen" section). this is the whole entire page, no skips, no cuts, we're doing all of it. grab a strawberry π and let's go.
β¨ NAME β¨
buildbox-run-oci β it's literally just buildbox-run-oci, that's the name, that's the girl π
π DESCRIPTION π
the vibe of this whole thing is:
usage: debian/buildbox/usr/bin/buildbox-run-oci [OPTIONS]
so you run that path, you throw some options at it, and it does its lil thing. all the options are down below, and there are a lot of them, so no skipping ahead, i'll know π«Ά
--helpβ prints this message and then dips. that's it, that's the whole job β¨--versionβ prints the version info and exits. short and sweet, we love a low-maintenance icon π--action=PATHβ the path to read the input Action from. that's where the Action is, bestie, go read it.--action-result=PATHβ the path to write the output ActionResult to. one goes in, one comes out, very balanced π--log-level=LEVELβ (default:info) how much gossip do you want in the logs? pick your fighter:trace/debug/info/warning/error.traceis the girl who tells you EVERYTHING,erroris the girl who only speaks when something's on fire π--verboseβ just sets the log level todebug. one-flag shortcut, we love efficiency β¨--digest-functionβ set the digest function. you pick it, it uses it, no further questions π--log-directory=DIRβ writes logs into this directory, and the filenames it uses are exactly this:
debian/buildbox/usr/bin/buildbox-run-oci.<hostname>.<username>.log.<severity level>.<date>.<time>.<pid>
like yes it's long, it's giving "my full legal name", but every piece of it is meaningful and we respect it πΈ
--disable-localcasβ do not use LocalCAS protocol methods. turning this on is a whole lifestyle change, just so you know π¦--workspace-path=PATHβ where on disk the runner hangs out and uses as its root when it's executing jobs. this is home base, periodt π--stdout-file=FILEβ the file that the command's stdout gets redirected into π--stderr-file=FILEβ same energy, but for stderr π©·--no-logs-captureβ do not capture and upload whatever got written to stdout and stderr. if you don't want it saved, this is the flag, no cap π--collect-execution-statsβ gathersexecution_stats.protometrics and attaches the digest of that message in CAS toActionResult.execution_metadata.auxiliary_metadata. yes it's a mouthful, yes it's correct, i don't make the rules β¨--validate-parametersβ just a check-up appointment: it verifies all the required parameters are actually being passed and that no unknown options showed up. it exits with a status code containing the result (0if successful). think of it as a vibe check before the real thing π§--post-action-command=COMMANDβ a command to run after the action is done. it can take one parameter, which is the path to the staged directory. heads up: these commands are blocking if--disable-localcasis set π₯--output-bypass-local-cacheβ skips caching output blobs in the LocalCAS storage when you're using the LocalCAS API. important: this has no effect if--disable-localcasis set. like, zero. nothing. nada π--staging-mode=MODEβ specifies how to stage directories and files when handlingStageTreeRequest. valid values are:[fuse, copy-or-link, default], wheredefaultwill favorfuseif it's available. choose wisely bestie π--graceful-shutdown-seconds=SECONDSβ how long to wait after sending a SIGTERM to the executed command, because of a timeout or a runner shutdown. and btw: by default a SIGKILL is sent immediately. no grace, no warning, just gone π--remote=URLβ URL for the CAS service π--instance=NAMEβ name of the CAS instance π·οΈ--server-cert=PATHβ public server certificate for TLS (PEM-encoded) π--client-key=PATHβ private client key for TLS (PEM-encoded) π--client-cert=PATHβ public client certificate for TLS (PEM-encoded) π--access-token=PATHβ access Token for authentication (e.g. JWT, OAuth access token, etc), and it will be included as an HTTP Authorization bearer token. very "she has credentials" of you π--token-reload-interval=MINUTESβ time to wait before refreshing the access token from disk again. you can optionally slap a suffix on it:M(minutes),H(hours). if you don't give a suffix, the value defaults to minutes. so no suffix = minutes, always β°--googleapi-authβ use GoogleAPIAuth when this flag is set. flag on, Google auth on πΈ--credential-helper=PATHβ path to the credential helper executable for dynamic authentication. example:--credential-helper=/usr/bin/helperπ§--retry-limit=INTβ number of times to retry on grpc errors. resilience queen πͺ--retry-delay=MILLISECONDSβ how long to wait before the very first grpc retry β³--retry-on-codeβ which gRPC status code(s) to retry on π--request-timeout=SECONDSβ how long to wait for gRPC request responses. patience has a limit, and this is it β--min-throughput=BPSβ minimum throughput in bytes per second. the value may be suffixed withK,M,GorT. so you can be dramatic about it if you want β¨--keepalive-time=SECONDSβ the period after which a keepalive ping is sent. just checking in, hope you're well π--load-balancing-policyβ which grpc load balancing policy to use. valid options are'round_robin'and'grpclb'π--ra-remote=URLβ URL for the Asset service ποΈ--ra-instance=NAMEβ name of the Asset instance π·οΈ--ra-server-cert=PATHβ public server certificate for TLS (PEM-encoded) π--ra-client-key=PATHβ private client key for TLS (PEM-encoded) π--ra-client-cert=PATHβ public client certificate for TLS (PEM-encoded) π--ra-access-token=PATHβ access Token for authentication (e.g. JWT, OAuth access token, etc), will be included as an HTTP Authorization bearer token π--ra-token-reload-interval=MINUTESβ time to wait before refreshing the access token from disk again. the following suffixes can be optionally specified:M(minutes),H(hours). value defaults to minutes if the suffix isn't specified β°--ra-googleapi-authβ use GoogleAPIAuth when this flag is set πΈ--ra-credential-helper=PATHβ path to credential helper executable for dynamic authentication. example:--credential-helper=/usr/bin/helperπ§--ra-retry-limit=INTβ number of times to retry on grpc errors πͺ--ra-retry-delay=MILLISECONDSβ how long to wait before the first grpc retry β³--ra-retry-on-codeβ which gRPC status code(s) to retry on π--ra-request-timeout=SECONDSβ how long to wait for gRPC request responses β--ra-min-throughput=BPSβ minimum throughput in bytes per second. the value may be suffixed withK,M,GorTβ¨--ra-keepalive-time=SECONDSβ the period after which a keepalive ping is sent π--ra-load-balancing-policyβ which grpc load balancing policy to use. valid options are'round_robin'and'grpclb'π--nested-instance=NAMEβ the instance to use for nested remote execution πͺ--nested-ac-enable-updateβ allow action cache updates for nested remote execution β
ok iconic reminder bestie: some of these interact. if--disable-localcasis set,--output-bypass-local-cachedoes literally nothing, and--post-action-commandcommands are blocking. and with no--graceful-shutdown-seconds, the SIGKILL comes immediately. love a flag that tells you the tea upfront π
and that's the whole page, fr fr, nothing left out π
buildbox-run-oci version 1.4.16, dated August 2026. shoutout to whoever wrote this and to whatever license you shipped it under, mwah, and to you for reading all 55-ish options like a true main character ππ bye bestie!
π¦ where this page comes from
- ubuntu stonking: buildbox 1.4.16+dfsg-1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms