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
For improved resiliance against Internet connectivity failures, it'd be ideal of allocators / docker engines could somehow get images from another node, rather than going to Docker hub all the time.
To support such a capability:
Allocators should be able to report images currently held on node (may or may not be running)
Allocators should be able to request transfer of image
Actual transfer can be done either by:
Setting up a per-host registry (or a subset of hosts with good network connectivity and bandwidth + disk capacity)
Save the image to a file, copy it, then load it (may take longer than prior solution)
The text was updated successfully, but these errors were encountered:
Their architecture seems like it has a lot of parts, wondering if it can be deployed with fewer components and in a simplified manner, so we get just the features we need.
Alternatively, need to look into using IPFS's existing protocols and libraries. It supports a replication factor to ensure certain content are replicated a minimum number of times, an ideal feature for images.
For improved resiliance against Internet connectivity failures, it'd be ideal of allocators / docker engines could somehow get images from another node, rather than going to Docker hub all the time.
To support such a capability:
The text was updated successfully, but these errors were encountered: