On 19/12/13 11:07, Bohuslav Kabrda wrote:
Hi all,
apart from dependencies versioning, there is another big feature I'd like to
implement - working with docker.io containers. I tried to sum this up at issue tracker
[1]. What we need to do:
* Find out what is the optimal development workflow with docker.io containers.
* Add a CommandRunner class that would create these containers.
* Document this feature.
* Actually use this in default assistant set.
Maybe we should modify package managers so that we can reuse them for installing
dependencies into containers - but I'm not sure about this. A second option would be
to just provide dockerfiles for certain projects, but that would mean that we can't
modify the containers/images... Do we want to modify these, too? :)
Thanks for all your comments/opinions/suggestions.
Slavek.
[1]
https://github.com/bkabrda/devassistant/issues/143
_______________________________________________
devassistant mailing list
devassistant(a)lists.fedoraproject.org
https://lists.fedoraproject.org/mailman/listinfo/devassistant I think that new
Command Runner will be needed. There are several
options for manipulating with images.
I think that Docker IO should be may be alone topassistant ???
Typical scenarios:
- list of docker images from repository
- create docker images from repository or from local machine
- run / append docker image
- delete docket image
- list of local docker images etc.
I think that modifications of docker images will be needed in the future:)
Sign up to the global docker.io repository.
This is my brainstorming.
Some workflow from yesterday persentation (presented by Jan Zeleny) was.
1) list a docker.io repository
2) create a docker.io image
3) run the docker.io image
4) append to the docker.io image
another workflow
1) commit a changes to a local repository
2) push the changes to the repository
3) push the images also to the global repositori
--
Best regards / S pozdravem
Petr Hracek