docker_container resource not idempotent ?

[0xAhmed]

Hi,

Thanks for the cookbook, I was wondering if it was not designed to be idempotent ?

I am basically using the docker_container resource, however with each chef run a new container is created !

Any hints ?

[bflad]

It should be idempotent in most if not all use cases. Can you send a sample recipe where you're not seeing the correct behavior? I'd also like to see the DEBUG output if possible. Thanks

[0xAhmed]

I am basically using it in an application/wrapper cookbook, just a simple recipe with the following content:

docker_container "docker-registry" do
    image "samalba/docker-registry"
    detach true
    hostname "xx.xx.xx.xx"
    port 5000
    env "SETTINGS_FLAVOR=local"
    volume "/mnt/docker:/docker-storage"
end

We're talking about DEBUG output of the chef-client here ?

[bflad]

Okay its not being idempotent because its currently using the command attribute to determine if it's running. I'll be able to take a look at this further tomorrow

[0xAhmed]

I see, It's just that a lot of docker containers just bake the CMD in their Dockerfiles, that was my case.

Extra thanks.

[bflad]

I had written the cookbook before dockerfiles existed. Just need to account for the newer use cases.

[bflad]

This should be fixed in 0.14 of the cookbook, which I'm releasing now. Please test and let me know if this doesn't work still.

[0xAhmed]

Awesome, will check it out now

[bflad]

Fixed in 0.14.0