You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be very useful to be able to specify the run command when committing a container, like in the case where some one needs to interact with Docker outside of Chef and may have no access to the run command specified in the recipe.
The text was updated successfully, but these errors were encountered:
Great idea. I was thinking of adding this from the get go, obviously I should've just done it. I'm thinking maybe runspec as the name for the attribute? Have you tried using the new actions? Do they work in your environment? I was implementing features ahead of my usage/testing.
I would suggest that you simply name it 'run' to simplify 'translation' between the docker CLI and cookbooks, though I guess that may be a moot point since other attributes already differ some what. Just my opinion. :)
I was happy to find the new support for importing from tarballs, though I may have stumbled across a bug that I'll have to investigate more tomorrow (attempting to import two in a row resulted in one or both succeeding depending on the ordering, so I don't know if it's just on my end yet).
It would be very useful to be able to specify the run command when committing a container, like in the case where some one needs to interact with Docker outside of Chef and may have no access to the run command specified in the recipe.
The text was updated successfully, but these errors were encountered: