How to increase build timeout

Issues information

Your issue

Is it possible to increase the build timeout? I’m getting this error:

Container image 
failed to be build: Cannot build Application "z64d16bc3" due to an error with docker: 
 { raw_error_message: "Killing process \"docker\" \"buildx\" \"build\" \"--progress=plain\" \"--network=host\" \"--output=type=registry\" \"--cache-from\" \"type=registry,\" \"-f\" \"/home/qovery/.qovery-workspace/965b5581-b513-46a6-b677-816be6187405-1-1654874873/build/z64d16bc3/Dockerfile\" 
\"--tag\" \"\" 
\"--tag\" \"\" 
\"/home/qovery/.qovery-workspace/965b5581-b513-46a6-b677-816be6187405-1-1654874873/build/z64d16bc3/\" due to timeout 1800s reached" }

Dockerfile content (if any)

FROM node:${NODE_VERSION} as installer

ARG BUILD_ENV=development
RUN echo "Build Environment: ${BUILD_ENV}"
RUN mkdir -p /usr/app
WORKDIR /usr/app
ADD package.json package-lock.json .npmrc ./
ADD lib lib
RUN npm i -g npm@8
RUN npm ci

# STAGE-2: Build the app (can leave this out if not running production)
FROM node:${NODE_VERSION} as builder

ARG BUILD_ENV=development
RUN echo "Build Environment: ${BUILD_ENV}"
WORKDIR /usr/app
COPY --from=installer /usr/app .
ADD . .
RUN npm run build

# STAGE-3: Finalize (TODO: We only really need a subset of these folders)
WORKDIR /usr/app
COPY --from=builder /usr/app .
# TODO: Clean up folders not in use, remove node_modules, reinstall production dependencies


CMD ["npm", "start"]

Hi @dmansouri ,

It’s possible to increase build timeout up to what you need. However, it’s not yet configurable via the web console. But it is via our API.

You simply need to:

  1. Install the Qovery CLI to generate an API token.
  2. Run the following curl command:
curl -X PUT -h "Authorization: Token <your API token>" \
-d '{"build.timeout_max_sec": 3600}' \

Note: to find your app ID, copy/paste your URL and take the ID after /applications/


Here, the app ID is 62d072c-4b28-4b60-9747-baabccd5f888

Thanks, @rophilogene. That got me past the first timeout. I’m now seeing something else that I can’t quite figure out. Searching this forum, I see another user who had a similar issue, but I’m not sure what this means:

deployment error application z64d16bc3 : error => EngineError { tag: HelmChartUninstallError, event_details: EventDetails { provider_kind: None, organisation_id: QoveryIdentifier { raw_long_id: "z30070ce1", short: "z30070ce" }, cluster_id: QoveryIdentifier { raw_long_id: "9d6b1e5c-b449-4b44-ad67-b60134d78e51", short: "9d6b1e5c" }, execution_id: QoveryIdentifier { raw_long_id: "965b5581-b513-46a6-b677-816be6187405-2-1654897576", short: "965b5581" }, region: None, stage: Environment(Deploy), transmitter: Application("z64d16bc3", "z64d16bc3", "34d6176a7feda28ff19784b671af66cb17d825c0") }, user_log_message: "Helm timed out for release `application-z64d16bc3-z64d16bc3` during helm UPGRADE: Error: release application-z64d16bc3-z64d16bc3 failed, and has been uninstalled due to atomic being set: timed out waiting for the condition: Error while executing Helm command. / Full details: ExitStatusError(ExitStatus(unix_wait_status(256)))", underlying_error: None, link: None, hint_message: None }

@dmansouri , it seems that your app fails to start because of not enough memory - can you check your memory settings in your Qovery app?

Thanks, @rophilogene. How did you determine that from the error message above? Is there something I could have looked at so I don’t bother you with this next time?

That’s exactly why we are working on Qovery V3. It’s a complete rewrite of our web interface to give much more insights into what’s going on. It will be possible directly from the V3 web interface.

In the meantime, the only way is to connect to your Kubernetes cluster and debug manually why your application fails to start with this kind of error.

Note: I can put you in the loop for Qovery V3 - soft launch for the end of this month.

That would be great! Please put me on the beta list for V3. Looking forward to it.

1 Like