---
title: "Virtual Windows machine for checking R packages"
author: "Tomas Kalibera"
date: 2021-03-18
categories: ["Testing", "Windows", "Package Development"]
tags: ["UCRT", "virtual machine"]

---



<p>Microsoft provides a free Windows 10 virtual machine for testing. Package
maintainers working on Linux and MacOS can use it to test their packages on
Windows. See <a href="https://developer.r-project.org/WindowsBuilds/winutf8/ucrt3/vm.html">instructions</a>
on how to set up the machine automatically for checking R packages.</p>
<p>The set up provides SSH access with bash, so that users can perform most of
the tasks from their preferred terminal emulator. Command line tools needed
to build R and many R packages from source are pre-installed. Additional tools
are available via pacman package manager, including e.g. vim editor.</p>
<p>The instructions show how to download R and the experimental UCRT toolchain
with libraries to build R and R packages.</p>
<div id="details" class="section level2">
<h2>Details</h2>
<p>One can also log in to the machine via graphical interface using a remote
desktop client, available for free for both Linux and MacOS. There is a
shared folder for transferring files.</p>
<p>Unlike e.g. Docker containers, this is a usual computer intended for
interactive use, with state saved on the (virtual) hard disk, which survives
across reboots of the virtual machine as well as the host (Linux or macOS)
machine. One can create/restore snapshots of that state.</p>
<p>However, one should not save important state on the machine as there is a
90-day limit on use for testing. Please check the license terms when
downloading.</p>
<p>The instructions were tested now on Ubuntu 20.04 and macOS 11.2.3.</p>
<p>It is recommended to install the machine only via fast un-metered connection.
Expect close to 10G to be downloaded, including the original VM image itself
and the toolchain.</p>
<p>Please see the <a href="https://developer.r-project.org/WindowsBuilds/winutf8/ucrt3/vm.html">instructions</a>
to get started.</p>
</div>
<div id="internals" class="section level2">
<h2>Internals</h2>
<p>The setup uses <a href="https://www.vagrantup.com/">vagrant</a> to configure
(“provision”) and manage the virtual machine in
<a href="https://www.virtualbox.org">virtualbox</a>.</p>
<p>The provisioning includes:</p>
<ul>
<li><p>setting up SSH: allowing incoming connections, inserting a public key for
connecting without a password, starting SSH server on boot</p></li>
<li><p>setting up RDP: allowing incoming connections, disabling NLA to allow
older clients to connect</p></li>
<li><p>installing MSys2, including bash, also with unzip, diffutils, make,
winpty, rsync, texinfo, tar, texinfo-tex, zip, subversion, bison,
moreutils, xz, patch</p></li>
<li><p>installing Inno Setup and MikTeX</p></li>
</ul>
<p>Individual provisioning steps are then implemented in PowerShell. Vagrant
communicates with the VM using WinRM protocol, which is enabled by default
in this VM.</p>
</div>
<div id="limitations" class="section level2">
<h2>Limitations</h2>
<p>There is the 90-day limit, but even instructions on the background of the VM
suggest to re-install after it expires.</p>
<p>Some console applications won’t work from SSH, including MikTeX. Hence, one
cannot build the R installer from the SSH connection. However, one can
still build R and probably most R packages.</p>
<p>Some R operations on Windows use graphical interface by default. When
working from SSH, one can sometimes disable that, e.g.
<code>options(menu.graphics=FALSE)</code> before installing packages.</p>
<p>The machine is set up for simplicity, not security. The intended use is
notebooks or single-user workstations running inside a trusted home/office
network, ideally still with a firewall on the machine, used for testing and
debugging R packages. See comments in the <code>Vagrantfile</code> for details.</p>
<p>The version of Windows 10 in this machine is so old that R cannot use UTF-8
as the native encoding. It is still good for testing packages with the UCRT
toolchain, many potential issues would not be encoding-related. Also, the
current CRAN checks run with Latin 1 encoding as well.</p>
</div>
<div id="references" class="section level2">
<h2>References</h2>
<ol style="list-style-type: decimal">
<li><p><a href="https://developer.r-project.org/WindowsBuilds/winutf8/ucrt3/vm.html">Setting up a virtual machine to check R packages.</a>
Instructions to set up and use the VM. Including the experimental UCRT build of R and
toolchain, but [2] has additional details on that.</p></li>
<li><p><a href="https://developer.r-project.org/WindowsBuilds/winutf8/ucrt3/howto.html">Howto: UTF-8 as native encoding in R on Windows.</a>
Instructions for the experimental UCRT build of R and toolchain.</p></li>
</ol>
</div>