Open
Description
Since the last update was half a year ago, I really need to ask, if this project is still alive?
I am having a problem, not sure what exactly the problem is...
🐛 Bug description
Whenever I build my rust-project using cargo, everything works fine. As soon as I try sls package using the plugin, I am getting:
Serverless: Running "serverless" installed locally (in service node_modules)
Serverless: Configuration warning at 'provider.runtime': should be equal to one of the allowed values [dotnetcore2.1, dotnetcore3.1, go1.x, java11, java8, java8.al2, nodejs10.x, nodejs12.x, nodejs14.x, provided, provided.al2, python2.7, python3.6, python3.7, python3.8, python3.9, ruby2.5, ruby2.7]
Serverless:
Serverless: Learn more about configuration validation here: http://slss.io/configuration-validation
Serverless:
Serverless: Building Rust user-api.me func...
Serverless: Running containerized build
error: no matching package named `lambda_runtime_api_client` found
location searched: https://github.com/awslabs/aws-lambda-rust-runtime/#a7e17ee4
required by package `lambda_runtime v0.4.1 (https://github.com/awslabs/aws-lambda-rust-runtime/#a7e17ee4)`
... which is depended on by `lambda_http v0.4.1 (https://github.com/awslabs/aws-lambda-rust-runtime/#a7e17ee4)`
... which is depended on by `user-api v0.1.0 (/code)`
Serverless: Rust build encountered an error: undefined 1.🤔 Expected Behavior
The build should run free of failures and create package.
👟 Steps to reproduce
- Checkout this project
- make sure
sls packageworks - update the Cargo.toml as follows(this is updating lambda_http and tokio):
tokio = { version = "1.15.0", features = ["macros"] }
lambda_http = { version = "0.4.1", git = "https://github.com/awslabs/aws-lambda-rust-runtime/", branch = "master"}
serde_json = "1.0.73"If you now run cargo build the build works fine. But using sls package throws the error mentioned above.
🌍 Your environment
- windows 10 x64
- rustup 1.24.3
- npm 8.3.0
- node 17.2.0
{
"devDependencies": {
"serverless": "^1.74.1",
"serverless-rust": "^0.3.8"
}
}
I guess this might be related to the docker image (?!?)
So am I the only one using the default docker image? If so, is there a newer alternative you can hint me at?
The experimental "dockerless" option works.
This is why I am wondering if this project is still under development...
Metadata
Metadata
Assignees
Labels
No labels