Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

DockerImageAsset is missing build context

See original GitHub issue

I’m submitting a …
- 🪲 bug report
- 🚀 feature request
- 📚 construct library gap
- ☎️ security issue or vulnerability => Please see policy
- ❓ support request => Please see note at the top of this template.
What is the current behavior? If the current behavior is a 🪲bug🪲: Please provide the steps to reproduce

Right now there is not option to specify the build context for the docker build. E.g. if the Dockerfile requires files from .. the build context need to be at least ‘…’ instead of ‘.’ which is the default.

What is the expected behavior (or behavior of feature suggested)?

There should be an option to specify the context. This could be tricky, since CDK stages the files which would then mean to stage the entire build context.

What is the motivation / use case for changing the behavior or adding this feature?

It is an advanced use case for building docker images in for example mono-repositories where there are dependencies into other folders.

Please tell us about your environment:
- CDK CLI Version: 0.36.0
- Module Version: 0.36.0
- OS: all
- Language: TypeScript
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc)