The intention for this package is to have a nice abstract interface for users to control components of yannt that need to run in their own containers.
Note: At the moment, this is really on a stub package only because it may be overly complicated for users to have the dependency to support docker in docker.
The intention is to have yannt installed in the outer environment and then different versions of yannt in a inner environment. The following commands are use cases where we want to generate some kind of model file but we need to de-conflict dependencies which could be as subtle as package version constraints and as extreme as different python runtime versions.
yannt cri transformers [args]
yannt cri yolo [args]The idea is that purely yannt code (e.g. pparse and sysscan) can exist in a more host oriented context. Things that have weird dependency requirements or constraints will be isolated in containers for ease of maintenance and development. The cri subcommand intends to abstract the underlying container commands. I'd like to support podman and docker with a bias towards podman for permission purposes. ... all TBD.
For now, out of simplicity, I am going to lean more on independent packages for things like transformers and yolo so users can choose to manage that in their own separate Python runtimes (i.e. kernels) or virtual environments.