Skip to content

DockerImageAsset is missing build contextΒ #3342

@KnisterPeter

Description

@KnisterPeter
  • 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)

Metadata

Metadata

Assignees

Labels

@aws-cdk/assetsRelated to the @aws-cdk/assets packageclosing-soonThis issue will automatically close in 4 days unless further comments are made.feature-requestA feature should be added or improved.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions