git push caution main No Procfile found after commit #220

modalala commented 2026年05月01日 08:06:55 +02:00

Following quickstart docs:

(https://docs.caution.co/quickstart/ > https://docs.caution.co/quickstart/fully-managed/#deploy-the-application)

success running caution init -

Initializing new deployment...
Git repository found
Created Procfile in current directory
Edit the required 'run' field to match your application
Build precedence: build: -> containerfile: -> repo-root Containerfile -> Dockerfile
Learn more: https://docs.caution.co/reference/procfile/
Procfile found
Build command: docker build -t app .
App created!
ID: <ID>
Name: frost-tools
State: initialized
Git URL: ssh://git@dashboard.caution.co:2222/<ID>.git
Added git remote 'caution': ssh://git@dashboard.caution.co:2222/<ID>.git

Then, I made some edits and committed the Procfile to the local repo.
Then, git push caution main

remote: [x] Preparing deployment...
remote: error: No Procfile found in repository root. Please add a Procfile with a required `run:` field and either `build:` or `containerfile:`. If both are absent, Caution auto-detects a repo-root `Containerfile` before `Dockerfile`.
remote: error: Invalid deployment response
error: failed to push some refs to 'ssh://dashboard.caution.co:2222/5<ID>.git'

It appears to me that the deployed app does not include the Procfile because it was not committed when originally running caution init, and that there was no update to the newly committed state with git push caution main. However I have not tried to confirm this exact sequence of events, yet.

related: #121

Following quickstart docs: (https://docs.caution.co/quickstart/ > https://docs.caution.co/quickstart/fully-managed/#deploy-the-application) success running `caution init` - ``` Initializing new deployment... Git repository found Created Procfile in current directory Edit the required 'run' field to match your application Build precedence: build: -> containerfile: -> repo-root Containerfile -> Dockerfile Learn more: https://docs.caution.co/reference/procfile/ Procfile found Build command: docker build -t app . App created! ID: <ID> Name: frost-tools State: initialized Git URL: ssh://git@dashboard.caution.co:2222/<ID>.git Added git remote 'caution': ssh://git@dashboard.caution.co:2222/<ID>.git ``` Then, I made some edits and committed the `Procfile` to the local repo. Then, `git push caution main` ``` remote: [x] Preparing deployment... remote: error: No Procfile found in repository root. Please add a Procfile with a required `run:` field and either `build:` or `containerfile:`. If both are absent, Caution auto-detects a repo-root `Containerfile` before `Dockerfile`. remote: error: Invalid deployment response error: failed to push some refs to 'ssh://dashboard.caution.co:2222/5<ID>.git' ``` It appears to me that the deployed app does not include the Procfile because it was not committed when originally running `caution init`, and that there was no update to the newly committed state with `git push caution main`. However I have not tried to confirm this exact sequence of events, yet. related: #121

modalala commented 2026年05月02日 03:19:22 +02:00

caution apps list returns:
<ID> - <repo_name> (failed)

caution apps get returns:

App Details:
 ID: <ID>
 Name: <repo_name>
 State: failed

caution apps build returns:

Building EIF locally for inspection...
✓ Application image built: caution-local-build:70533cc38b95
Error: Procfile must specify 'binary' field

Then, after changing Procfile, with the binary field uncommented and populated, committing and pushing , I have got a new error having to do with a building script. So now I believe this error is probably because of a malformed Procfile, not a missing Procfile - which would indicate an inaccurate error message. I'll continue testing.

`caution apps list` returns: `<ID> - <repo_name> (failed)` `caution apps get` returns: ``` App Details: ID: <ID> Name: <repo_name> State: failed ``` `caution apps build` returns: ``` Building EIF locally for inspection... ✓ Application image built: caution-local-build:70533cc38b95 Error: Procfile must specify 'binary' field ``` Then, after changing `Procfile`, with the `binary` field uncommented and populated, committing and pushing , I have got a new error having to do with a building script. So now I believe this error is probably because of a malformed `Procfile`, not a missing `Procfile` - which would indicate an inaccurate error message. I'll continue testing.

modalala commented 2026年05月08日 08:42:52 +02:00

Today, on

commit e8590b39ef0d9643e0087cb0701abd8731e02576 (HEAD -> main, caution/main, caution/HEAD)
Merge: b3d1a5d d40922a
Author: RyanSquared <ryan@distrust.co>
Date: Tue May 5 23:01:06 2026 -0400
 Merge branch 'ryansquared/handle-duplicate-eif'

I did a caution init in a git repo already containing a Procfile :

Procfile found
Build command: docker buildx build -f ./docker/Dockerfile . --platform linux/amd64
App created!
ID: <ID>
Name: app-<8hex>
State: initialized

then, I edited the Procfile, commited locally, then ran git push caution main and got:

remote: error: No Procfile found in repository root. Please add a Procfile with a required `run:` field and either `build:` or `containerfile:`. 

The Procfile had both of these fields.

Today, on ``` commit e8590b39ef0d9643e0087cb0701abd8731e02576 (HEAD -> main, caution/main, caution/HEAD) Merge: b3d1a5d d40922a Author: RyanSquared <ryan@distrust.co> Date: Tue May 5 23:01:06 2026 -0400 Merge branch 'ryansquared/handle-duplicate-eif' ``` I did a `caution init` in a git repo already containing a `Procfile` : ``` Procfile found Build command: docker buildx build -f ./docker/Dockerfile . --platform linux/amd64 App created! ID: <ID> Name: app-<8hex> State: initialized ``` then, I edited the Procfile, commited locally, then ran `git push caution main` and got: ``` remote: error: No Procfile found in repository root. Please add a Procfile with a required `run:` field and either `build:` or `containerfile:`. ``` The Procfile had both of these fields.

modalala commented 2026年05月08日 08:58:20 +02:00

I repeated the same process, but started the repo without a Procfile, let caution init generate one, and then committed the altered Procfile - I got the same result with an error message saying there is no Procfile.

I repeated the same process, but started the repo without a `Procfile`, let `caution init` generate one, and then committed the altered `Procfile` - I got the same result with an error message saying there is no Procfile.

modalala commented 2026年05月08日 09:10:48 +02:00

I was not able to reproduce this with demo-hello-world-enclave

I have a sense this is because of something in my app's Procfile which is causing a failure to read-in the file on the server, perhaps?

I was _not_ able to reproduce this with `demo-hello-world-enclave` I have a sense this is because of something in my app's `Procfile` which is causing a failure to read-in the file on the server, perhaps?

ryansquared commented 2026年06月29日 12:15:28 +02:00

procfile is dead, caution.hcl parser produces better errors, closing.

procfile is dead, caution.hcl parser produces better errors, closing.