Cannot deploy to Caprover

[Turab]

Hi.

I would like to deploy on a production site (on Caprover), but I cannot, because when I want to build from Github, it stops at helm project which return HTTP 404. (Clicking on it in the source also ends-up with HTTP 404.)

How can I deploy on a PaaS like Caprover? Dockerfile wouldn't work as it first needs the files to be locally available for it to be able to run the "copy" commands in the Dockerfile.

Submodule 'apps/telephony' (git@github.com:open-condo-software/condo-telephony.git) registered for path 'apps/telephony'
Submodule 'apps/telephony-ws-api' (git@github.com:open-condo-software/condo-telephony-ws-api.git) registered for path 'apps/telephony-ws-api'
Submodule 'apps/ticket-importer' (git@github.com:open-condo-software/condo-ticket-importer.git) registered for path 'apps/ticket-importer'
Cloning into '/captain/temp/image_raw/open-condo/5/source_files/.helm'...
ERROR: Repository not found.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: clone of 'ssh://git@github.com:22/open-condo-software/infrastructure-condo.git' into submodule path '/captain/temp/image_raw/open-condo/5/source_files/.helm' failed
Failed to clone '.helm'. Retry scheduled
Cloning into '/captain/temp/image_raw/open-condo/5/source_files/apps/announcements'...
ERROR: Repository not found.
fatal: Could not read from remote repository.
.....

[toplenboren]

Hello! Thanks for the issue! 🚀

Helm is our internal project with infrastructure configurations, project is available to function properly without it and without any other private submodules..

I'm not familiar with capover, but you can try to deploy this project instead: https://github.com/open-condo-software/open-condo-platform – it is just a copy of https://github.com/open-condo-software/condo but with all private submodules removed

Alternatively you can try to fork the repo, remove submodules, edit the dockerfile / change logo? / change translations? and then try to deploy it

Please feel free to reach out to us if any of the ways above wouldnt work, good luck!

[Turab]

Thank you. But it still stops at a copy command complaining it can't find the file.

Step 11/33 : COPY --chown=app:app ./out /app
{"message":"COPY failed: file not found in build context or excluded by .dockerignore: stat out: file does not exist"}

[pahaz]

Could you please provide us with some step-by-step instructions how to reproduce your problem? At the moment, we have a CI check for the Open Source part. https://github.com/open-condo-software/condo/actions/runs/17094879389/job/48476907110

[Turab]

Actually I am relying on the automated building process of Caprover.

1- I cloned the repository so that I could make necessary changes if needed during building process. (Here it is: https://github.com/Turab/open-condo-platform.git)

2- Enter Github access token and the repo URL on the interface and click the build button.

The result is:

Build started for open-condo
Ignore warnings for unconsumed build-args if there is any
Step 1/33 : ARG REGISTRY=docker.io

Step 2/33 : FROM ${REGISTRY}/python:3.13-slim-bookworm AS python

---> 0cb54302c4d5
Step 3/33 : FROM ${REGISTRY}/node:22-bookworm-slim AS node

---> 955b467cb9a2
Step 4/33 : FROM ${REGISTRY}/buildpack-deps:bookworm AS base

---> 88971866a76d
Step 5/33 : COPY --from=python /usr/local/ /usr/local/

---> 1bb69af74b41
Step 6/33 : COPY --from=node /usr/local/ /usr/local/

---> be9f62de741c
Step 7/33 : COPY --from=node /opt/ /opt/

---> f4e56f6de064
Step 8/33 : RUN set -ex 	&& groupadd -r app --gid=999 	&& useradd --system --create-home --home /app --gid 999 --uid=999 --shell /bin/bash app 	&& rm -f /usr/local/bin/docker-entrypoint.sh 	&& python --version 	&& pip --version 	&& node --version 	&& yarn --version 	&& python3 -m pip install 'psycopg2-binary==2.9.10' && python3 -m pip install 'Django==5.2'     && echo "OK"

---> Running in cd577362c63f
+ groupadd -r app --gid=999

+ useradd --system --create-home --home /app --gid 999 --uid=999 --shell /bin/bash app

+ 
rm -f /usr/local/bin/docker-entrypoint.sh

+ python --version

Python 3.13.7
+ pip --version

pip 25.2 from /usr/local/lib/python3.13/site-packages/pip (python 3.13)
+ node --version

v22.18.0
+ yarn --version

1.22.22
+ python3 -m pip install psycopg2-binary==2.9.10

Collecting psycopg2-binary==2.9.10
Downloading psycopg2_binary-2.9.10-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (4.9 kB)
Downloading psycopg2_binary-2.9.10-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (3.0 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.0/3.0 MB 15.6 MB/s  0:00:00

Installing collected packages: psycopg2-binary
Successfully installed psycopg2-binary-2.9.10
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.

+ python3 -m pip install Django==5.2

Collecting asgiref>=3.8.1 (from Django==5.2)
Downloading asgiref-3.9.1-py3-none-any.whl.metadata (9.3 kB)
Collecting sqlparse>=0.3.1 (from Django==5.2)
Downloading sqlparse-0.5.3-py3-none-any.whl.metadata (3.9 kB)
Downloading Django-5.2-py3-none-any.whl (8.3 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 8.3/8.3 MB 29.3 MB/s  0:00:00

Downloading asgiref-3.9.1-py3-none-any.whl (23 kB)
Downloading sqlparse-0.5.3-py3-none-any.whl (44 kB)
Installing collected packages: sqlparse, asgiref, Django

Successfully installed Django-5.2 asgiref-3.9.1 sqlparse-0.5.3
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.

OK
+ echo OK

Step 9/33 : FROM base AS installer

---> 6fa054070629
Step 10/33 : WORKDIR /app

---> Running in e4f694fbe07c
---> Removed intermediate container e4f694fbe07c
---> d4d79b58d39b
Step 11/33 : COPY --chown=app:app ./out /app

{"message":"COPY failed: file not found in build context or excluded by .dockerignore: stat out: file does not exist"}
COPY failed: file not found in build context or excluded by .dockerignore: stat out: file does not exist
Build has failed!
----------------------
Deploy failed!
Error: {"message":"COPY failed: file not found in build context or excluded by .dockerignore: stat out: file does not exist"}
COPY failed: file not found in build context or excluded by .dockerignore: stat out: file does not exist

[pahaz]

The core issue is that the Condo project’s Dockerfile is designed for a multi‑stage build, where the ./out directory is created in earlier stages. However, when deploying directly via CapRover, those stages aren’t executed properly.

You can check the https://github.com/open-condo-software/condo/blob/main/docs/deploy.md docs.

TLDR: you need to run bash ./bin/warm-docker-cache before the build step.