Add initial gvisor contrib doc
							parent
							
								
									35f45d1930
								
							
						
					
					
						commit
						735cea8dfa
					
				| 
						 | 
				
			
			@ -0,0 +1,33 @@
 | 
			
		|||
---
 | 
			
		||||
linkTitle: "gvisor"
 | 
			
		||||
title: "Releasing a gvisor image"
 | 
			
		||||
date: 2019-09-25
 | 
			
		||||
weight: 10
 | 
			
		||||
---
 | 
			
		||||
 | 
			
		||||
## Prerequisites
 | 
			
		||||
 | 
			
		||||
* Credentials for `gcr.io/k8s-minikube`
 | 
			
		||||
* Docker
 | 
			
		||||
* Gcloud
 | 
			
		||||
 | 
			
		||||
## Background
 | 
			
		||||
 | 
			
		||||
gvisor support within minikube requires a special Docker image to be generated. After merging changes to `cmd/gvisor` or `pkg/gvisor`, this image will need to be updated.
 | 
			
		||||
 | 
			
		||||
The image is located at `gcr.io/k8s-minikube/gvisor-addon`
 | 
			
		||||
 | 
			
		||||
## Why is this image required?
 | 
			
		||||
 | 
			
		||||
`gvisor` requires changes to the guest VM in order to function. The `addons` feature in minikube does not normally allow for this, so to workaround it, a custom docker image is launched, containing a binary that makes the changes.
 | 
			
		||||
 | 
			
		||||
## What does the image do?
 | 
			
		||||
 | 
			
		||||
- Creates log directories
 | 
			
		||||
- Downloads and installs the latest stable `gvisor-containerd-shim` release
 | 
			
		||||
- Updates the containerd configuration
 | 
			
		||||
- Restarts containerd and rpc-statd
 | 
			
		||||
 | 
			
		||||
## Updating the gvisor image
 | 
			
		||||
 | 
			
		||||
`make push-gvisor-addon-image`
 | 
			
		||||
		Loading…
	
		Reference in New Issue