$ packer build -only=vmware-iso windows_2022_docker.json Step 1 (building the headless Vagrant box) can be done with these steps: docker run to run Windows containers in that Windows VM.Packer build or by using one of the pre-built Vagrant Cloud binaries vagrant up to create a running VM instance of Windows Server, either using the.(optional) packer build to build a Vagrant base box, it's like a Docker image, but.'Infrastructure as Code', so every build step is available on GitHub.

That uses the box images windows_2019_docker, respectivelyįirst you need a Windows Server VM for your hypervisor. Or vagrant up 2022-box to get your box image downloaded directly from VagrantĬloud. If you don't want to run the packer step, you can run vagrant up 2019-box The 1903 semi-annual version and with vagrant up insider the Insider build. So with a vagrant up 2019 you spin up the LTS version, with vagrant up 1903 lcow - Windows Server, version 1809 with LCOW enabled.insider - Windows Server Insider builds.2016 - Windows Server 2016 (3) LTS channel.2016-box - Windows Server 2016 (3) LTS channel, * prebuilt from Vagrant Cloud.1803 - Windows Server, version 1803 (4) Semi-Annual Channel.1809 - Windows Server, version 1809 (3) Semi-Annual Channel.1903 - Windows Server, version 1903 (2) Semi-Annual Channel.2019 - Windows Server 2019 (3) LTS Channel.2019-box - Windows Server 2019 (3) LTS Channel, prebuilt from Vagrant Cloud.2022 - Windows Server 2022 (8) LTS Channel.2022-box - Windows Server 2022 (8) LTS Channel, prebuilt from Vagrant Cloud.This is where youĭecide which Vagrant VM should be started. There are several versions of Windows Server. You can easily switch between Docker Desktop Linux This Vagrant environment creates a 'Docker Machine' to work on your MacBook with

Windows docker on mac with gui