Skip to content
This repository was archived by the owner on Jul 6, 2018. It is now read-only.

volumes are not mounting properly #85

Closed
jgoulah opened this issue Mar 16, 2016 · 3 comments
Closed

volumes are not mounting properly #85

jgoulah opened this issue Mar 16, 2016 · 3 comments

Comments

@jgoulah
Copy link
Contributor

jgoulah commented Mar 16, 2016

using the machine resource, I define volumes such as:
:volumes => ["/Users/testuser:/home/testuser"],

The docker run command that is issued does mount the volumes (if I run it manually it works), but then in the DockerContainerMachine::converge function the container is renamed and the volumes are lost (the directory exists but is not mounted, no files)

@jgoulah
Copy link
Contributor Author

jgoulah commented Mar 16, 2016

I'll also note that I think it was broken in this commit 07753c4#diff-82b3f52918fe92819012dcf0d787c347

If I change the code back to transport.execute it seems to keep the volumes mounted

@jgoulah
Copy link
Contributor Author

jgoulah commented Mar 16, 2016

At this point I can confirm when transport.container.commit is called none of the options are getting passed, and subsequently when image.run is called none of these options exist on the container, therefore the volumes are missing

I am not sure on the correct fix, I think we want to invoke Docker::Image.create with the correct options OR just call transport.execute as it was doing previous to the change above. Look forward to hearing thoughts

@jgoulah
Copy link
Contributor Author

jgoulah commented Mar 21, 2016

this works on the new master, however, there is another semi-related bug I'll submit a patch for

@jgoulah jgoulah closed this as completed Mar 21, 2016
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Development

No branches or pull requests

1 participant