5.1.1.4 Remote Build Context

A remote build context is any build context supplied as a URL rather than a local directory — a Git repository, a tarball hosted on a remote server — letting docker build fetch the context directly rather than requiring it to already exist on the local filesystem.

Building From a Remote Tarball

A URL pointing to a compressed archive can be used directly as a build context, with Docker fetching and extracting it before the build proceeds.

docker build -t myapp https://example.com/build-context.tar.gz

Building From a Git Repository

As with a dedicated Git context, a Git URL is one specific form of remote context, distinguished by Docker's awareness of Git-specific syntax such as branch and subdirectory references.

docker build -t myapp https://github.com/example/myapp.git

Why Remote Contexts Are Useful for Automation

Remote contexts are particularly useful for automated systems that need to trigger a build from a known, externally hosted source, without first needing to fetch and stage that source locally as a separate step.

curl -X POST https://ci.example.com/trigger-build \
  -d "context=https://github.com/example/myapp.git#$COMMIT_SHA"

Security Considerations of Remote Contexts

Because a remote context is fetched and built without the same local visibility into its exact contents that a local directory provides, building from a remote source — particularly one not fully trusted or controlled — carries some additional risk worth being deliberate about.

docker build -t myapp https://example.com/untrusted-context.tar.gz

Building from an unfamiliar or unverified remote source should generally be approached with the same caution as running any other unverified code, since the build process executes arbitrary instructions defined by whatever Dockerfile that remote context happens to contain.

Why Remote Build Context Matters

Remote build contexts extend docker build's flexibility beyond local directories, supporting automation-friendly workflows, but they also introduce a layer of trust consideration that a local directory context, fully visible before the build even starts, does not carry to the same degree.