Menu
BatectBatectDocsBundlesBlog
GitHubChat
BatectBatect
  • Docs
  • Bundles
  • Blog
  • GitHub
  • Chat
  • Getting started
    • Introduction
    • Hello world
    • System requirements
    • Installation
    • Tutorial
    • Sample projects
    • Shell tab completion
    • Comparison with other tools
  • Concepts
    • Projects
    • Tasks
    • Containers
    • Caches
    • Includes and bundles
    • Task lifecycle
    • Run as current user mode
  • Reference
    • Config file reference
      • Overview
      • Config variables
      • Containers
      • Includes
      • Tasks
      • Expressions
    • CLI reference
    • Cheat sheet
  • Using Batect with other tools and ecosystems
    • Overview
    • Cypress
    • Docker
    • Golang
    • Gradle
    • .NET Core
    • Node.js
    • Renovate
    • Ruby
    • Seq
  • Using Batect with CI systems
    • General advice
    • Buildkite
    • CircleCI
    • GitHub Actions
    • Travis CI
  • How to guides
    • IDE integration
    • Improve performance
    • Keep Batect and your configuration up-to-date
    • Migrate an existing codebase to use Batect
    • Migrate from Docker Compose
    • Stop build artefacts being owned by root
    • Wait for dependencies to be ready in integration tests
    • Work with network proxies

Containers

A container is the environment in which a command is run. It is based on a Docker image, along with other configuration such as environment variables.

A fresh container is created each time a task starts, and is destroyed when the task ends. This ensures that every time a task runs, it has a consistent environment to operate in.

Containers are never reused between tasks, even if both a task and one of its prerequisites needs the same container.

See also#

  • Configuration reference for containers
Edit this page
Previous
« Tasks
Next
Caches »
  • See also

Docs

  • Config file reference
  • CLI reference
  • Cheat sheet

Community

  • Bundles
  • GitHub
  • Chat

Legal

  • Privacy
Copyright © 2017-2021 Charles Korn.