[aws-ecs] On MacOS the fromImage filled the trash with content recursively and lock those files in Trash

[olivier-schmitt]

I tried to use aws_ecs.ContainerImage.from_asset('..') function to build a Docker image and to use it in a Fargate cluster.

At first, I failed to use this because the path was not correct and I had errors about paths and names being too long.

I fixed the path and went on.

Later on when I tried to empty the trash of my MacOS, I noticed I was not able to do so.

I found out that cdk assets were in the trash and I was not able to delete them.
I tried to remove all docker images related to the CDK and I noticed that the files in Trash seem to be a recursive tree:

Reproduction Steps

Probably by using a bad path in fromImage function.

What did you expect to happen?

Not to have such problem with the trash.

What actually happened?

• the trash says the files are used and I'm not able to delete them using the vairous UI techniques
• recursive tree of files which does not exists in my codebase

Environment

• CLI Version : (node:906) ExperimentalWarning: The fs.promises API is experimental
  1.67.0 (build 2b4dd71)
• Framework Version:
• Node.js Version: v10.16.3
• OS : MacOs 10.15.7
• Language (Version): Python 3.8

Other

---

This is 🐛 Bug Report

[MrArnoldPalmer]

hey @olivier-schmitt, when using fromAsset it's best to use path.resolve(__dirname, ...) when pointing to a file relative to your cdk source. Otherwise the path will be relative to the working directory where synth was run from. You may have discovered this already.

This occurs when you point to a Dockerfile that is in a directory that is a parent of the CDK app. There is a ticket for this here. I'm gonna close in favor of that one.

I reproduced and was able to remove the generated output by running rm -r cdk.out.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.