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

lifecycle: failed with status code: 62 #2665

Closed
alixeb opened this issue Jan 22, 2025 · 3 comments
Closed

lifecycle: failed with status code: 62 #2665

alixeb opened this issue Jan 22, 2025 · 3 comments

Comments

@alixeb
Copy link

alixeb commented Jan 22, 2025

Hello 👋

toto-fn % kn func version
v0.43.1
toto-fn % kn func run
A registry for function images is required. For example, 'docker.io/tigerteam'.
? Registry for function images: alixeb/sandbox/toto-fn
Note: building a function the first time will take longer than subsequent builds
Building function image
Still building
Still building
Yes, still building
Don't give up on me
Still building
Error: executing lifecycle: failed with status code: 62
Error: exit status 1
// func.yaml
specVersion: 0.36.0
name: toto-fn
runtime: node
created: 2025-01-22T07:34:09.369608Z

The folder was generated with func create -l node toto-fn and there is no code changes (from what was generated)

OS: Mac OS Sequoia 15.1
Chip: Apple M1 Pro

Why is building the function toto-fn fails with Error: executing lifecycle: failed with status code: 62?
I am using Docker Desktop and I am sign in. alixeb/sandbox is a private registry on Docker

Help much appreciated.

@matejvasek
Copy link
Contributor

This could be caused by fact the buildpack strategy does not support arm64 for most languages (Java and Go are supported).
Try switching to s2i strategy func build --builder=s2i.

@matejvasek
Copy link
Contributor

Also you could try build with verbose flag to see more output: func build -v.

@alixeb
Copy link
Author

alixeb commented Jan 24, 2025

Thanks my issue is resolved.

@alixeb alixeb closed this as completed Jan 24, 2025
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

2 participants