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
{{ message }}
This repository has been archived by the owner on Aug 14, 2020. It is now read-only.
It would be superbly beneficial if the docker2api tool provided support for caching layers. In other words, the amount of data that needs to be transferred would be minimized in case of small incremental updates or when the image on docker hub did not change since last time docker2aci was run. This would be especially useful in context of big images that include many binary dependencies (common in containerized academic applications). The cache could be stored in the home folder by default.
The text was updated successfully, but these errors were encountered:
As most of appc, docker2aci is currently not in active development mode so this new feature is not currently on the radar. However, we'll gladly accept PRs from any interested contributors!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be superbly beneficial if the docker2api tool provided support for caching layers. In other words, the amount of data that needs to be transferred would be minimized in case of small incremental updates or when the image on docker hub did not change since last time docker2aci was run. This would be especially useful in context of big images that include many binary dependencies (common in containerized academic applications). The cache could be stored in the home folder by default.
The text was updated successfully, but these errors were encountered: