No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

It looks like you're using `@pulumi/awsx` version 1 -- is that right?

You shouldn't have to "wait" for the image to be created -- the `immage: imggWebDev.imageUri` should take care of that. :thinking_face:

I am I’ll try update my awsx version! And yes I read that passing the uri as I have should wait for it to be available and complete 

<@U062MJN98Q2> did you ever manage to solve this? I'm getting a similar error

&gt; Container.image repository should be 255 characters or less
which i believe is because it's passing in the whole `OutputImpl { __pulumiOutput: true, ...` object as a string instead of waiting for it to resolve to a value. so i've tried the various things you've tried. hard coding the full imageUri works for me though so it has to be not resolving the string as expected

<@UMRF75FAA> hello, apologies I moved job and have only come back to the community now. 

I did by upgrading the awsx version to &gt; 2.* which had its own challenges of breaking some classes but once I solved them it began to work again. 

But I did try a few other options before, such as ensuring the promise resolved before the image was used, hardcoding etc but that didn’t solve my issue 

interesting. i'm already on awsx 2.* so that's not it i don't think

I don't suppose you still have the code you could look at to see if anything obvious jumps out at you do you?

Unfortunately I do not as I’m not longer at that company but leave it with me and I’ll see if I can’t find anything else I did, try get back to you tomorrow 

I had

```    containerDefinitions: pulumi
      .all([image])
      .apply(([image]) =&gt; { ...```
instead of

```    containerDefinitions: pulumi
      .all([image.imageUri])
      .apply(([image]) =&gt; { ...```
which immediately resolved obviously because image existed and it didn't wait for the imageUri property to exist

:man-facepalming:

thanks offering to look into it for me, much appreciated

Oh yeah I have done the same! Can be a pain to spot so good job catching it! 

Happy to help! 

Thank you <@UMRF75FAA> for mentioning this! It’s a super subtle thing and easy to miss, and I’ve definitely hit this myself before too. We’re in the process of refreshing our input/output docs and I’ve shared this with the team so we can get it better documented.