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 error #595

Open
dawk0 opened this issue Jan 14, 2025 · 1 comment
Open

Build error #595

dawk0 opened this issue Jan 14, 2025 · 1 comment
Labels

Comments

@dawk0
Copy link

dawk0 commented Jan 14, 2025

Describe the bug

Hi developers,

we are trying to deploy your instance schedular by pipeline. The pipeline inherits from an alpine image and has the following versions installed:

Node: v18.20.1
Npm: 9.6.6
Python 3.11.10
Poetry (version 2.0.0)
Running the following commands from your instructions

npm ci
npx cdk bootstrap
npx cdk deploy instance-scheduler-on-aws

result in an error:

Bundling asset instance-scheduler-on-aws/MetricsUuidGenerator/Code/Stage...
sending incremental file list
sent 38 bytes  received 12 bytes  100.00 bytes/sec
total size is 0  speedup is 0.00
Poetry could not find a pyproject.toml file in /asset-output or its parents


Error: Failed to bundle asset instance-scheduler-on-aws/MetricsUuidGenerator/Code/Stage, bundle output is located at <path>/build/cdk.out/asset.f9834392b6a445b537520c9cdc12189cfb283f14ddd77802b367d72c03a528d9-error: Error: docker exited with status 1
--> Command: docker run --rm -u "0:0" ...

Note that we also tried to only run npx cdk synth or to use the build script in /deployment/build-s3-dist.sh which both result in in the same error.

Is the pyproject.toml missed in bundling the python lambda functions?
Thanks for any help in advance!

To Reproduce

Try to build the whole solution in a clean env.

Expected behavior

Expected would be that everything is there to build the solution.
Maybe we are missing something - any help is appriciated.

@dawk0 dawk0 added the bug label Jan 14, 2025
@CrypticCabub
Copy link
Member

Thanks for reaching out, what you describe is definitely an unusual error but here are a few things I would try:

-Install and run projen from the root (npm install projen, projen). Instance Scheduler uses projen to generate and maintain all of the packaging files (including the pyproject.toml).

-Ensure your environment has access to docker -- the build process has a dependency on docker for building the lambda dependencies

I've also added a task to our backlog to review the current build instructions.

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

No branches or pull requests

2 participants