-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(aws-ecr-assets): TarballImageAsset Fails in Stage #24827
Comments
Unfortunately I can't get this reproduced. I am using CDK in TypeScript as the following code: class MyStack extends cdk.Stack {
constructor(scope: Construct, id: string, props?: StackProps) {
super(scope, id, props);
new ecrassets.TarballImageAsset(this, "image", {
tarballFile: path.join(__dirname, '../demo.tar')
});
}
}
class MyStage extends cdk.Stage {
constructor(scope: Construct, id: string) {
super(scope, id)
new MyStack(this, "mystack-test")
}
}
new MyStage(app, 'mystage-dev') I generate
I am not sure if it only happens in Java or is it tarball-specific. Can you generate a new tarball just as what I did above and see if the issue still exists? |
The busybox image also fails in my application. I tried building a reproducer (https://github.com/gilday/cdk-issue-24827), but I'm unable to reproduce whatever it is about my other project that makes this fail. I'm on macOS, and in the Console, I see error messages from
|
I am experiencing the same (CDK v2.75.0). I gave a look at the cdk repo (in particular The file is saved at the root of the folder while the I tried to manually move the generated |
Any updates on this? |
Are you able to reproduce this error using my code snippet here? |
Describe the bug
The
TarballImageAsset
construct fails when it is nested inside of aStack
that is also inside of aStage
. Moving thatStack
outside of theStage
works around the issue.Expected Behavior
The
TarballImageAsset
should push the image to ECR.Current Behavior
The failure occurs when
TarballImageAsset
attempts to shell out todocker load
.Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.70.0 (build c13a0f1)
Framework Version
2.70.0
Node.js Version
v19.8.1
OS
macOS 13.2.1
Language
Java
Language Version
17.0.6
Other information
Consider sending requests to the Docker daemon without shelling out to the Docker CLI to get more descriptive errors and avoid issues like #19627.
The text was updated successfully, but these errors were encountered: