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
We currently have FALLBACK_IMAGE. If an devcontainer is not specified, we should also support a KITCHENSINK_IMAGE (or use the fallback image for this too). Then, an admin can maintain an image that works in "most" cases.
The text was updated successfully, but these errors were encountered:
We have several customers heavily using the kitchensink image approach, I think we should invest in this so that an envbuilder template can be a generic template.
Open question: is fallback image good enough, or is there a rationale to have both?
We currently have
FALLBACK_IMAGE
. If an devcontainer is not specified, we should also support aKITCHENSINK_IMAGE
(or use the fallback image for this too). Then, an admin can maintain an image that works in "most" cases.The text was updated successfully, but these errors were encountered: