https://pulumi.com logo
Join Slack
Powered by
```Diagnostics: docker:index:Image (12fda807-con...
# aws
s
Copy code
Diagnostics:
  docker:index:Image (12fda807-container):
    error: Docker native provider returned an unexpected error from Configure: failed to connect to any docker daemon

  pulumi:pulumi:Stack (dockerfile-default-dev):
    error: awsx:ecr:Image resource 'app-img' has a problem: grpc: the client connection is closing

Resources:
    + 31 created
q
Is docker running on your system? The error 
failed to connect to any docker daemon
usually means that docker isn't running or the provider cannot connect to it
s
Oh! I have to start it locally? It doesn't connect to one up on AWS?
q
Yes, docker needs to be running locally where you execute pulumi (your local machine, CI, etc.)
s
Ahh cool, it works now.
Interesting.
q
If you're interested in remote image builders, I'd recommend you to look into Docker BuildKit and the Pulumi docker-build provider: https://www.pulumi.com/registry/packages/docker-build/ That would allow you to start a remote builder and use that to run the image build. For example, you could run the builder on a kubernetes cluster: https://docs.docker.com/build/builders/drivers/kubernetes/ But beware that this setup is more complex than a regular local build
s
Nice, looks interesting. Yeah I'm still learning all this, just switching from SST.
For some reason I thought the Docker container would have been built externally up on AWS in the ECR/ECS. Been a while since I've dockered anything at all.
20 Views
Open in Slack
PreviousNext
Powered by