Some common start up issues are shown below, if you want anything added please make a request on GitHub issues.
If you are using one of the templates (e.g. RStudio) then they are launched within Docker. A guide on how it uses them are in this article.
The base VM that launches the Docker container is a custom Google stripped down version that only runs Docker and not other common linux commands such as apt-get
, since their intention is you use those commands within the Docker containers running.
This means if you want to install dependencies, you should either:
Dockerfile
to install the dependencies. docker exec -it {container name} bash
to drop into bash running within the container. For RStudio, this would be docker exec -it rstudio bash
gcloud SDK
so a quick way to ensure this is to install the gcloud SDK and authenticate through there.gce_ssh(vm, username = "goodusername")
docker_*
commands such as docker_cmd()
rely on SSH, so make sure SSH is working correctly (see above) and you can run gce_ssh()
correctly. A guide on using build triggers is here, that may help. Common issues include:
docker ps -a
command (or docker_cmd(vm, "ps -a")
) returns your Docker image name. If it doesn't it has not downloaded or found your imagerstudio
as that username is reserved0.2.0
or greater, that ensure ports 80/443 are open in your default network. (port 8787 is not required)docker ps
container_logs()
to see if there was an issue on start up.v0.2.0
is it doesn't allow project ids with numbers. Either use a project Id without numbers or load the GitHub version that fixes the bugAny scripts or data that you put into this service are public.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.