Troubleshooting / Known issues

Help! My function isn’t working! All I get is a 404/blank page!

In the very first alpha release of STACKIT Functions, we don’t have support for checking the status of a function or reading logs in the STACKIT Functions CLI / runtime.

Here is a checklist of things that are easy to get wrong, while we are still working on providing better error feedback from the CLI itself.

• Try running the function locally, using sfn function build followed by sfn function run. If the function runs into errors while starting up, the STACKIT runtime would never be able to forward requests to it.
• Make sure you supply valid registry pull credentials. Pass --registry-id to sfn function deploy or have one registry ID configured in your stackit-functions.yaml manifest; otherwise, the STACKIT Functions won’t be able to pull your image. You can get the ID of a registry from sfn config registries list. See also, Registry access.

If you still don’t know why your function is failing to start, please get in touch!

Deploying a function results in a 502 Bad Gateway error

This means that the STACKIT Functions runtime was unable to read your OCI image’s metadata from the OCI Registry.

Ensure you supply the right Registry credentials and use the --registry-id flag when calling sfn function deploy. Otherwise, the runtime won’t be able to access the image.

I get a dependency-related error when building an image

Please report the issue to us–it’s possible that we have missed an issue in the template / build process that needs ironing out for your usecase.

Consider building your images with Dockerfile if the supplied buildpacks fail to work for you.