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
@pkubatrh Ah, thanks. I thought the incremental build feature of s2i was kinda buggy/unfinished. So I would probably wait to see how it works out for nodejs, see if they can work out the kinks before implementing it here.
I think this would really help adoption. Right now, using s2i means waiting for a really slow build vs. a Dockerfile where requirements.txt would be cached.
So, If I understand it correctly from the node and go containers, it should work for Python container like this:
Users prepare their own Dockerfile, where they call the save-artifacts script which basically creates a tarball from the main virtual environment with all app dependencies already installed.
Then, during a second build, if the tarball is provided in /tmp/artifacts, it's extracted to the original location (virtual environment).
Assemble script still tries to install all dependencies but because some or ideally all of them are already there, the second build is much faster.
Is that correct?
I don't use s2i because it does not support podman so is there any significant difference when s2i is used and a user does not have to prepare its own dockerfile manually?
Activity
frenzymadness commentedon Mar 19, 2019
Could you please provide more info? What do you mean by incremental builds and why is this important?
torsava commentedon Mar 19, 2019
@omron93 Do we use incremental builds in other containers?
pkubatrh commentedon Mar 19, 2019
@torsava soon in nodejs: sclorg/s2i-nodejs-container#201
torsava commentedon Mar 19, 2019
@pkubatrh Ah, thanks. I thought the incremental build feature of s2i was kinda buggy/unfinished. So I would probably wait to see how it works out for nodejs, see if they can work out the kinks before implementing it here.
omron93 commentedon Mar 23, 2019
@pkubatrh @torsava https://github.com/sclorg/golang-container supports incremental builds for some time already. I'm not aware of any problems with it. @jcajka Are you?
jtratner commentedon Jun 27, 2019
I think this would really help adoption. Right now, using s2i means waiting for a really slow build vs. a Dockerfile where requirements.txt would be cached.
wjhrdy commentedon Aug 20, 2021
I just found this article about how to make incremental builds work using s2i python container. https://developpaper.com/using-s2i-to-build-images-from-source-code/
frenzymadness commentedon Aug 23, 2021
So, If I understand it correctly from the node and go containers, it should work for Python container like this:
/tmp/artifacts, it's extracted to the original location (virtual environment).Is that correct?
I don't use s2i because it does not support podman so is there any significant difference when s2i is used and a user does not have to prepare its own dockerfile manually?
frenzymadness commentedon Nov 10, 2026
Inactive issue for years, closing.