Build Logs

Build logs show exactly what happens while Atlasflow turns your commit into a container image. They stream live as the build runs and remain available on the deployment afterward.

# Where to find them

Open a deployment from your project and select its build logs. While a build is in progress, the logs update in real time; once it finishes, you can scroll back through the full output.

# What you'll see

Build logs are organized around the build's structure:

• Steps: the stages of your build (for example installing dependencies, compiling, producing the final image), each with a state such as running, complete, cached, or failed.
• Progress: progress indicators for long-running operations like downloading layers.
• Log lines: the raw output from each step, tagged with a severity level (info, warning, or error).

A step marked cached means Atlasflow reused a previous result, which speeds up the build. See Builds for how caching works.

# Reading a failed build

When a build fails, the failing step is marked with an error and the log lines for that step usually contain the cause, for example a missing dependency, a failing compile step, or a bad Dockerfile instruction.

# Next steps

• Runtime logs: logs from your running container.
• Builds: the build pipeline.
• Troubleshooting: common build failures.