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
The first hurdle is building the container. My original idea was to use make .venv an artifact. However this doesn't work because virtualenv hardcodes the full path name.
I'd rather not package the entire build environment into a pod's running container. A Go container rarely weighs in at more than 100 Mi; so far python containers are well over 1 Gi.
I'm curious if this is a use case this tool is ever used for?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The first hurdle is building the container. My original idea was to use make .
venv
an artifact. However this doesn't work because virtualenv hardcodes the full path name.I'd rather not package the entire build environment into a pod's running container. A Go container rarely weighs in at more than 100 Mi; so far python containers are well over 1 Gi.
I'm curious if this is a use case this tool is ever used for?
Beta Was this translation helpful? Give feedback.
All reactions