googleComputeEngineR (version 0.2.0)

gce_vm_template: Create a template container VM

Description

This lets you specify templates for the VM you want to launch It passes the template on to gce_vm_container

Usage

gce_vm_template(template = c("rstudio", "shiny", "opencpu", "r-base",
  "example", "dynamic", "ropensci"), username = NULL, password = NULL,
  dynamic_image = NULL, image_family = "cos-stable", ...)

Arguments

template

The template available

username

username if needed (RStudio)

password

password if needed (RStudio)

dynamic_image

Supply an alternative to the default Docker image here to download

image_family

An image-family. It must come from the cos-cloud family.

...

Arguments passed on to gce_vm_container

file

file location of a cloud-init file. One of file or cloud_init must be supplied

cloud_init

contents of a cloud-init file, for example read via readChar(file, nchars = 32768)

image_family

An image-family. It must come from the google-containers family.

Value

The VM object

Details

Templates available are:

• rstudio An RStudio server docker image with tidyverse and devtools

• shiny A Shiny docker image

• opencpu An OpenCPU docker image

• r_base Latest version of R stable

• ropensci RStudio and tidyverse with all ropensci packages on CRAN and Github

• example A non-R test container running busybox

• dynamic Supply your own docker image to download such as rocker/verse

For dynamic templates you will need to launch the docker image with any ports you want opened, other settings etc. via docker_run.

Use dynamic_image to override the default rocker images e.g. rocker/shiny for shiny, etc.

Examples

# NOT RUN {
# }
# NOT RUN {
 library(googleComputeEngineR)
 
 ## make instance using R-base
 vm <- gce_vm_template("r-base", predefined_type = "f1-micro", name = "rbase")
 
 ## run an R function on the instance within the R-base docker image
 docker_run(vm, "rocker/r-base", c("Rscript", "-e", "1+1"), user = "mark")
 #> [1] 2
 

# }
# NOT RUN {

# }