-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Open
Labels
feature: workspace-imagesmeta: never-staleThis issue can never become staleThis issue can never become staletype: feature requestNew feature or requestNew feature or request
Description
Is your feature request related to a problem? Please describe
Gitpod uses workspace-full image as the default workspace images for repos which do not have .gitpod.yml file. I want to configure the default workspace image for all such repos at a central place.
Describe the behaviour you'd like
Given the user wants to configure the default workspace images for all their workspace without a .gitpod.yml file.
When the user navigates to settings menu.
Then they should see an option to configure default workspace image for all their workspaces.
Describe alternatives you've considered
- Provide an option to the user to input the default image when user tries to create a workspace. However, this does not really solve the problem as they would need to input it every time.
- Use users' github/gitlab etc user settings to infer the default image - This will add complexity as the user will need to manage the settings outside of gitpod.
Additional context
Based on initial request raised here gitpod-io/workspace-images#680
felladrin, purkhusid and loujaybee
Metadata
Metadata
Assignees
Labels
feature: workspace-imagesmeta: never-staleThis issue can never become staleThis issue can never become staletype: feature requestNew feature or requestNew feature or request
Type
Projects
Status
No status
Milestone
Relationships
Development
Select code repository
Activity
jldec commentedon Feb 14, 2022
Added to WebApp Team project inbox.
@princerachit - one workaround is to use a dotfile to install missing tools on workspace startup.
axonasif commentedon Feb 15, 2022
Cross-Related issue: #6275 #8200
[-]Allow configuration of default workspace image in the user dashboard[/-][+]Custom, per-user, default workspace image[/+]stale commentedon Jul 13, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
jrmcdonald commentedon Aug 13, 2022
This feature would still be useful to me. I appreciate the issue has been closed due to inactivity though. Would it be best for me to raise a new feature request or can this one be reopened?
In my case my base image has tools installed that would timeout if I tried to install them via the dotfiles support.
SamB commentedon Jan 10, 2023
I personally was thinking it would be best if it could be pattern-based, so for example I could set the default workspace image for everything under https://salsa.debian.org to
debian:unstable
(or some other Debian image).