containersolutions / imagewolf Goto Github PK

Current PoC only supports swarm, but it should be easy to get working on k8s. First step is figuring out how to get list of peers.

If DOCKER_CONTENT_TRUST were set to 1, and notary were on the PATH (by building it into a child image of ImageWolf), I'd expect the nodes to verify the content through notary since docker load allegedly doesn't do that.

Should be able to define which images are pushed to nodes e.g. all images with "production" label. Would be nice to also be able to push to nodes with a given label e.g. just push this image to the "web tier".

The docker load calls cause high CPU and mem usage. I believe quayctl solves this problem by doing a docker pull from a temporary reg set up on the local node.

Is this abandoned? will this functionality be integrated into https://github.com/ContainerSolutions/trow?

Hi,

I have this idea, not all k8s clusters allow incoming connections and that would make listening for registry events unusable, for those scenarios, maybe there could be a service sitting next to the registry that would listen for the registry events and generating an RSS feed from them Imagewolf would subscribe to the feed and pull new images when available.

What do you think?

Currently there is a horrible hack to get nodes to use the local image where we explicitly use the digest. Need to find a better solution.