Build Logs

Build logs show the complete output of the process that creates the container image for your application. You can follow them in real time or review them after the build completes.

Viewing logs in real time

During an active build, logs are streamed in real time in the dashboard:

1. Go to the service page
2. Navigate to the Deployments tab
3. Click on the deployment that is in progress
4. Logs appear automatically and update in real time

The log viewer auto-scrolls to follow new lines. You can pause auto-scroll to analyze a specific section.

Build stages

Build logs show three main phases:

1. Source download — Guara Cloud downloads the source code from your repository at the specific commit
2. Image build — the container image is built from your code, installing dependencies and compiling the application
3. Image push — the built image is stored for use in the deploy

Debugging failed builds

When a build fails, logs are the primary tool for identifying the problem. Here are the most common errors and how to fix them:

“Cannot find module” or “Module not found”

Cause: A dependency is missing or the import path is incorrect.

Solution:

• Check that all dependencies are listed in package.json (Node.js) or the equivalent file for your language
• Make sure the imported file exists and the path is correct
• Run npm install or yarn install locally to confirm it works

”Port already in use” or port error

Cause: The application is not using the port configured in the service.

Solution:

• Configure your application to use the PORT environment variable
• Verify the port configured in the service matches the port your application listens on
• In most frameworks, use process.env.PORT (Node.js) or equivalent

”Build timeout”

Cause: The build exceeded the 15-minute time limit.

Solution:

• Optimize your Dockerfile to use layer caching efficiently
• Use a .dockerignore file to exclude unnecessary files (such as node_modules, .git)
• Consider upgrading your plan for more build resources

”Out of memory” or “Killed”

Cause: The build consumed more memory than allowed.

Solution:

• Reduce memory usage during the build (for example, avoid parallel builds)
• Use multi-stage builds in your Dockerfile to optimize the process
• Consider upgrading your plan for more resources

Highlighted error lines

The log viewer automatically highlights lines containing errors in red, making it easy to quickly identify problems. Log lines from the repository clone process can be expanded or collapsed to keep focus on the main build.