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
Not sure what you're after but running bita inside a container should be no different than running it on a host. And using bita to transfer container images (if the image is a file) should be no different than any using it to transfer any other file.
What im saying is doing the whole process of update based on one base container image and his next version, and apply the changes on tje container image files. Something like balenaEngine does and CargoSync.
Yeah, that's what bita does - Delta update of a file from one version to another. It doesn't care what kind of file it is, container image or what else, though it may work more or less efficient depending on the file content.
Activity
oll3 commentedon Jan 15, 2025
No container expert here. What's missing to achieve what you want?
jvdrag commentedon Jan 17, 2025
The same functionality but with container images
oll3 commentedon Jan 18, 2025
Not sure what you're after but running bita inside a container should be no different than running it on a host. And using bita to transfer container images (if the image is a file) should be no different than any using it to transfer any other file.
jvdrag commentedon Jan 18, 2025
What im saying is doing the whole process of update based on one base container image and his next version, and apply the changes on tje container image files. Something like balenaEngine does and CargoSync.
oll3 commentedon Jan 20, 2025
Yeah, that's what bita does - Delta update of a file from one version to another. It doesn't care what kind of file it is, container image or what else, though it may work more or less efficient depending on the file content.