Dev Environments do use VS Code though, and devcontainer.json is not an alternative to Compose but can work with it. Docker has its own support for Dev Environments in Docker Desktop but this is currently for local use only. gitpod.yml working.”Īnother remarked that it would “be nice if there was some open governed group maintaining standards like these for devtools.”ĭocker was cooler on the idea, with a spokesperson telling us it was “all Microsoft” and pointing us towards its Compose specification, though also emphasising that it does collaborate. Users like the idea, with one even finding lack of interoperability a blocker, saying “after running into this issue I ended up losing interest in Gitpod and not pursuing it further. Supporting it will allow us to lower the entry barrier for teams who already use it so they can easily spin up their dev environments in Gitpod,” Efftinge said last year. “Given VS Code’s and GitHub’s dominance in the developer world, VS Code’s devcontainer.json format is going to become a quasi-standard eventually. gipod.yml, but users have found the differences a source of friction, causing Gitpod co-founder Sven Efftinge to work on support for devcontainer.json, even before Microsoft’s recent announcement.
#MICROSOFT VISUAL STUDIO CODE UBUNTU CONTAINER PC#
With the CLI installed, and a devcontainers.json configured, a developer can start up a development environment on the local PC equally as easily as on Codespaces, hooked to the same GitHub repository.īut is the Microsoft-sponsored Development Containers specification just for Microsoft or something that will get wide adoption? Gitpod has its own YAML-based equivalent. Visual Studio Code used devcontainers.json for this, developed for the remote containers extension first released in 2019 and now also used in Codespaces.Īt the same time as Microsoft introduced the open source development containers spec, it also released a CLI (command line interface) as a reference implementation. The starting point is the container image but there is also a requirement to configure the container with mount points, environment variables, startup tasks, port forwarding, and other customizations.
Microsoft’s diagram explaining the roles of dev containersĪ key part of this process is defining the target environment, which in most cases is based on one or possibly several containers. The appeal of remote development is not only the ability to work from any machine, but also having predictable, reproducible and disposable development environments, rather than the traditional developer PC with all sorts of tools and dependencies installed. Gitpod, a pioneer of this approach, integrates with GitHub, Gitlab and with Jetbrains Gateway, and spins up developer environments in remote containers.
Jetbrains has an IDE backend that runs remotely allowing developers to code locally while compiling and debugging on the remote machine. Remote development is a hot area in developer tools. Last month, Microsoft declared that “dev containers have become broadly useful for scenarios beyond VS Code” and introduced an open source development containers specification which formalizes a configuration file called devcontainers.json and the capabilities it supports.
0 kommentar(er)
