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

Hey, I’m trying to use Pulumi to build and run docker containers locally. When I call pulumi destroy however, the running containers aren’t killed - do I have to kill them myself…?

Can you share some code? They should be destroyed I think

Image from iOS.jpg

So pretty simple, just build and run a container. Pulumi up works just fine.

But then when I run Pulumi destroy, that container is still running

Any ideas you might have  <@U01FB0HRB2Q> would be greatly appreciated 

What version of pulumi and the docker provider are you running?

If I run the following mine gets deleted. I'm running the latest versions of pulumi and docker provider:

```import * as docker from "@pulumi/docker";

const nginx = new docker.RemoteImage("nginxRemote", {
    name: "nginx"
});

const nginxContainer = new docker.Container("nginxlocal", {
    image: nginx.latest,
    ports: [{
        external: 8080,
        internal: 80
    }]
})```

Interesting, they should both be latest, but I’ll check. Thanks so much for providing a working example, I’m sure I’ll figure it out given this is true. I’ll let you know what I find, I’d guess it’s something to do with rm or something 

<@U01FB0HRB2Q> the use of the `rm`  option appears to be my issue. By adding it to your example, I get this issue:
```Diagnostics:
  docker:index:RemoteImage (nginxRemote):
    error: deleting urn:pulumi:local::mast::docker:index/remoteImage:RemoteImage::nginxRemote: Unable to remove Docker image: Error response from daemon: conflict: unable to remove repository reference "nginx" (must force) - container ff381712dcfd is using its referenced image d1a364dc548d

  pulumi:pulumi:Stack (mast-local):
    error: update failed```
when running destroy.

Given that it looks like pulumi clears up the file system that would be removed by rm on destroy anyway (?) - I'm pretty sure I can just not use this option. But it was certainly confusing.