Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build fails if no process types defined ("ERROR: failed to export: determining entrypoint: tried to set web to default but it doesn't exist") #41

Open
edmorley opened this issue May 8, 2024 · 0 comments

Comments

@edmorley
Copy link

edmorley commented May 8, 2024

The CNB spec permits there being no process types in an image (due to no buildpacks having set a process type):
https://github.com/buildpacks/spec/blob/main/buildpack.md#launchtoml-toml

Accordingly, the Pack CLI also permits this. eg:

$ git clone https://github.com/heroku/python-getting-started && cd $_
$ rm Procfile  # emulate the user not having defined any process types
$ pack build --builder heroku/heroku:22 python-test
...
===> EXPORTING
Adding layer 'heroku/python:dependencies'
Adding layer 'heroku/python:python'
Adding layer 'buildpacksio/lifecycle:launch.sbom'
Adding 1/1 app layer(s)
Adding layer 'buildpacksio/lifecycle:launcher'
Adding layer 'buildpacksio/lifecycle:config'
Adding label 'io.buildpacks.lifecycle.metadata'
Adding label 'io.buildpacks.build.metadata'
Adding label 'io.buildpacks.project.metadata'
no default process type
Saving python-test...
*** Images (401af57dbb7e):
      python-test
Adding cache layer 'heroku/python:pip-cache'
Adding cache layer 'heroku/python:python'
Successfully built image python-test

However, if Tekton tries to perform a build where no process types were defined, it errors:

===> EXPORTING
Adding layer 'heroku/python:dependencies'
Adding layer 'heroku/python:python'
Adding layer 'buildpacksio/lifecycle:launch.sbom'
Adding 1/1 app layer(s)
Adding layer 'buildpacksio/lifecycle:launcher'
Adding layer 'buildpacksio/lifecycle:config'
Adding label 'io.buildpacks.lifecycle.metadata'
Adding label 'io.buildpacks.build.metadata'
Adding label 'io.buildpacks.project.metadata'
ERROR: failed to export: determining entrypoint: tried to set web to default but it doesn't exist

This was reported in:
heroku/buildpacks-python#196

It seems the Tekton integration is not currently spec compliant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant