bootstrap problem with deployment on lambda

[rsignell-usgs]

I tried the deployment on lambda, and I'm failing on the bootstrap step:

(/scratch/my-conda-envs/titiler) ubuntu@ip-10-0-13-236:/scratch/titiler/deployment/aws$ npm run cdk bootstrap aws://${AWS_ACCOUNT_ID}/us-west-2

> [email protected] cdk
> cdk "bootstrap" "aws://313654087598/us-west-2"

jsii.errors.JavaScriptError:
  Error: spawnSync docker ENOENT
      at Object.spawnSync (node:internal/child_process:1086:20)
      at Object.spawnSync (node:child_process:693:24)
      at dockerExec (/tmp/jsii-kernel-AbxjMO/node_modules/@aws-cdk/core/lib/bundling.js:127:34)
      at Function.fromAsset (/tmp/jsii-kernel-AbxjMO/node_modules/@aws-cdk/core/lib/bundling.js:37:24)
      at /tmp/tmpxf_d82nf/lib/program.js:7991:114
      at Kernel._wrapSandboxCode (/tmp/tmpxf_d82nf/lib/program.js:8582:24)
      at /tmp/tmpxf_d82nf/lib/program.js:7991:87
      at Kernel._ensureSync (/tmp/tmpxf_d82nf/lib/program.js:8563:28)
      at Kernel.sinvoke (/tmp/tmpxf_d82nf/lib/program.js:7991:34)
      at KernelHost.processRequest (/tmp/tmpxf_d82nf/lib/program.js:9479:36)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/scratch/titiler/deployment/aws/cdk/app.py", line 203, in <module>
    titilerLambdaStack(
  File "/scratch/my-conda-envs/titiler/lib/python3.9/site-packages/jsii/_runtime.py", line 83, in __call__
    inst = super().__call__(*args, **kwargs)
  File "/scratch/titiler/deployment/aws/cdk/app.py", line 54, in __init__
    image=core.BundlingDockerImage.from_asset(
  File "/scratch/my-conda-envs/titiler/lib/python3.9/site-packages/aws_cdk/core/__init__.py", line 1603, in from_asset
    return jsii.sinvoke(cls, "fromAsset", [path, options])
  File "/scratch/my-conda-envs/titiler/lib/python3.9/site-packages/jsii/_kernel/__init__.py", line 128, in wrapped
    return _recursize_dereference(kernel, fn(kernel, *args, **kwargs))
  File "/scratch/my-conda-envs/titiler/lib/python3.9/site-packages/jsii/_kernel/__init__.py", line 359, in sinvoke
    response = self.provider.sinvoke(
  File "/scratch/my-conda-envs/titiler/lib/python3.9/site-packages/jsii/_kernel/providers/process.py", line 362, in sinvoke
    return self._process.send(request, InvokeResponse)
  File "/scratch/my-conda-envs/titiler/lib/python3.9/site-packages/jsii/_kernel/providers/process.py", line 326, in send
    raise JSIIError(resp.error) from JavaScriptError(resp.stack)
jsii.errors.JSIIError: spawnSync docker ENOENT
Subprocess exited with error 1
 1

Do I need to be the account owner to do this? I'm currently using an IAM user with Admin rights.

[kylebarron]

Just checking, Docker is running on your machine? Seems similar to some errors I've seen when docker isn't running

[rsignell-usgs]

Hey there @kylebarron ! Thanks for helping out!

Indeed, Docker was not running (I didn't know it needed to be!).

But I just did sudo snap install docker (I'm on ubuntu) and now it's installed!

So now I'm getting a different error on the bootstrap command:

(/scratch/my-conda-envs/titiler) ubuntu@ip-10-0-13-236:/scratch/titiler/deployment/aws$ npm run cdk bootstrap aws://313654087598/us-west-2

> [email protected] cdk
> cdk "bootstrap" "aws://313654087598/us-west-2"

jsii.errors.JavaScriptError:
  Error: [Status 1] stdout:


  stderr: unable to prepare context: path "/scratch/titiler/deployment/aws" not found
      at dockerExec (/tmp/jsii-kernel-XOfFZe/node_modules/@aws-cdk/core/lib/bundling.js:133:19)
      at Function.fromAsset (/tmp/jsii-kernel-XOfFZe/node_modules/@aws-cdk/core/lib/bundling.js:37:24)
      at /tmp/tmpd3582l2q/lib/program.js:7991:114
      at Kernel._wrapSandboxCode (/tmp/tmpd3582l2q/lib/program.js:8582:24)
      at /tmp/tmpd3582l2q/lib/program.js:7991:87
      at Kernel._ensureSync (/tmp/tmpd3582l2q/lib/program.js:8563:28)
      at Kernel.sinvoke (/tmp/tmpd3582l2q/lib/program.js:7991:34)
      at KernelHost.processRequest (/tmp/tmpd3582l2q/lib/program.js:9479:36)
      at KernelHost.run (/tmp/tmpd3582l2q/lib/program.js:9442:22)
      at Immediate._onImmediate (/tmp/tmpd3582l2q/lib/program.js:9443:46)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/scratch/titiler/deployment/aws/cdk/app.py", line 203, in <module>
    titilerLambdaStack(
  File "/scratch/my-conda-envs/titiler/lib/python3.9/site-packages/jsii/_runtime.py", line 83, in __call__
    inst = super().__call__(*args, **kwargs)
  File "/scratch/titiler/deployment/aws/cdk/app.py", line 54, in __init__
    image=core.BundlingDockerImage.from_asset(
  File "/scratch/my-conda-envs/titiler/lib/python3.9/site-packages/aws_cdk/core/__init__.py", line 1603, in from_asset
    return jsii.sinvoke(cls, "fromAsset", [path, options])
  File "/scratch/my-conda-envs/titiler/lib/python3.9/site-packages/jsii/_kernel/__init__.py", line 128, in wrapped
    return _recursize_dereference(kernel, fn(kernel, *args, **kwargs))
  File "/scratch/my-conda-envs/titiler/lib/python3.9/site-packages/jsii/_kernel/__init__.py", line 359, in sinvoke
    response = self.provider.sinvoke(
  File "/scratch/my-conda-envs/titiler/lib/python3.9/site-packages/jsii/_kernel/providers/process.py", line 362, in sinvoke
    return self._process.send(request, InvokeResponse)
  File "/scratch/my-conda-envs/titiler/lib/python3.9/site-packages/jsii/_kernel/providers/process.py", line 326, in send
    raise JSIIError(resp.error) from JavaScriptError(resp.stack)
jsii.errors.JSIIError: [Status 1] stdout:


stderr: unable to prepare context: path "/scratch/titiler/deployment/aws" not found
Subprocess exited with error 1

Obviously that path exists locally, but is this a path inside the container that is not found?
If so, it seems I might need some volume mounts?
Did I miss some whole Docker setup step?

[rsignell-usgs]

@vincentsarago , just pinging you here because I'm not sure that discussions trigger notifications?

[vincentsarago]

I did get the notification but I don't have time to look right now!

[rsignell-usgs]

@vincentsarago , okay, good to know I don't need to ping you and also good to know you are too busy to help right now!

[vincentsarago]

I haven't had any problem deploying with the lastest code. I'll mark this as answered.