I doubt anything other than Windows will be supported as long as Dev Box is built upon Windows 365. So if you need Ubuntu or other Linux distros, your only option is what WSL provides
That's a great video on devbox, very explanatory. Thank you for you effort. Do you may know what would be the optimal process to update a devbox image? Let's say my project now need a specific new tool to be available and pre-configured for all the devbox users (developers). I understand that I would need to have a new version of the devbox image (eg 1.0.0 -> 1.1.0) . How the existing devboxes would then be updated? Best would be not to loose any of the existing user created content in the current devboxes and just update/add what is new. Would this be possible?
Thanks for the feedback ❤️ Any existing dev boxes will not be updated whenever you publish a new version of an image, unfortunately. You would need to have your uses delete their dev boxes and recreate them. Agree that it would be nice to have the dev boxes be updated instead, but as far as I know that's not possible. I guess you could deploy any updates/new things through Endpoint Manager, but it kinda goes against the philosophy that the dev boxes are meant to be short-lived and purpose built. That being said, I know that one of the top priorities for the product group for Dev Box is to speed up deployment. Currently I usually see it taking around 30 minutes to deploy a dev box but their goal is to get that down to below 10 minutes (if I remember correctly). If they get are able to speed up the deployment that much I really don't see any benefit to updating dev boxes as opposed to recreating them. As long as you can store everything you need in the cloud and not locally on the dev boxes at least :)
Can we create install tools that we need on a dev box and then export image to add to the gallery and create new dev box definitions? Our development requires some tools to be installed on the dev box and we ideally do not want to repeat these steps for each developer.
It's not recommended to use an existing Dev Box for the basis of a new image, but it is doable. But I would rather opt for setting up 1, or at least few, initial image which contains the tools all your devs need. The image will be bloated yes, but it will make your life a lot easier.
Theoretically yes, but I would keep them separate. There are slightly different requirements for images for Dev Box/Windows 365 and Azure Virtual Desktop. And if you are planning to use Azure Virtual Desktop I would assume multi-session is in your plans and Dev Box/Windows 365 does not support multi-session editions of windows.
![EP 10: Windows 365 VS Microsoft Dev Box [Windows 365 Masterclass Series]](http://i.ytimg.com/vi/GcgAIBQ1-f8/mqdefault.jpg)
How do you feel about custom images in Dev Box? Is it to cumbersome to use or was it simpler than expected?
Do you know if ubuntu or any other OS ever going to be supported as a dev box?
I doubt anything other than Windows will be supported as long as Dev Box is built upon Windows 365. So if you need Ubuntu or other Linux distros, your only option is what WSL provides
Great stuff! Thanks
Glad you liked it!
That's a great video on devbox, very explanatory. Thank you for you effort. Do you may know what would be the optimal process to update a devbox image? Let's say my project now need a specific new tool to be available and pre-configured for all the devbox users (developers). I understand that I would need to have a new version of the devbox image (eg 1.0.0 -> 1.1.0) . How the existing devboxes would then be updated? Best would be not to loose any of the existing user created content in the current devboxes and just update/add what is new. Would this be possible?
Thanks for the feedback ❤️
Any existing dev boxes will not be updated whenever you publish a new version of an image, unfortunately. You would need to have your uses delete their dev boxes and recreate them.
Agree that it would be nice to have the dev boxes be updated instead, but as far as I know that's not possible.
I guess you could deploy any updates/new things through Endpoint Manager, but it kinda goes against the philosophy that the dev boxes are meant to be short-lived and purpose built.
That being said, I know that one of the top priorities for the product group for Dev Box is to speed up deployment. Currently I usually see it taking around 30 minutes to deploy a dev box but their goal is to get that down to below 10 minutes (if I remember correctly).
If they get are able to speed up the deployment that much I really don't see any benefit to updating dev boxes as opposed to recreating them. As long as you can store everything you need in the cloud and not locally on the dev boxes at least :)
Can we create install tools that we need on a dev box and then export image to add to the gallery and create new dev box definitions? Our development requires some tools to be installed on the dev box and we ideally do not want to repeat these steps for each developer.
It's not recommended to use an existing Dev Box for the basis of a new image, but it is doable. But I would rather opt for setting up 1, or at least few, initial image which contains the tools all your devs need. The image will be bloated yes, but it will make your life a lot easier.
Can these images used in Azure Virtual Desktop to provision to users?
Theoretically yes, but I would keep them separate. There are slightly different requirements for images for Dev Box/Windows 365 and Azure Virtual Desktop.
And if you are planning to use Azure Virtual Desktop I would assume multi-session is in your plans and Dev Box/Windows 365 does not support multi-session editions of windows.