<commit_before>---
title: Updating the OS (and other packages) your VM
author: <NAME>
categories: [understanding vm, koding]
template: page.toffee
---

# Updating the OS on your Koding VM

This guide will walk you through the process of upgrading the OS, Kernel and core packages on your Koding VM.

We will walk through the following steps:
1. Updating the packages (strictly update the current packages)
2. Updating the distribution/OS (install newly released packages)

So depending on your need, you can do 1) or 2) or both.

> type:alert
> Even though we have tested upgrading the VM, some updates may render your VM inaccessible so please proceed only if you know what you are doing. If you run into problems, you can always re-init your VM or send us a request via [<EMAIL>](mailto:<EMAIL>).


### A few prep commands
To get started, log into your Koding account and check what version of the OS and Kernel that
you currently have by typing the following command in Terminal:
```
uname -rv
```
this should return you something like this:
```
3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC 2014
```
Make a note of the kernel version, you can reference it later to ensure that the kernel update
worked.

You should also take a note of available disk space before you begin to ensure that you have adequate
space for all the updates. To get available disk space, type this command in Terminal:<commit_msg>added warning re: ubuntu 15.xx<commit_after>---
title: Updating the OS (and other packages) your VM
author: <NAME>
categories: [understanding vm, koding]
template: page.toffee
---

# Updating the OS on your Koding VM
> type:alert
> DO NOT update the OS to Ubuntu 15.xx, it will completely hose your VM and you will
> need to [reinit](http://learn.koding.com/faq/vm-reinit/)

This guide will walk you through the process of upgrading the OS, Kernel and core packages on your Koding VM.

We will walk through the following steps:
1. Updating the packages (strictly update the current packages)
2. Updating the distribution/OS (install newly released packages)

So depending on your need, you can do 1) or 2) or both.

> type:alert
> Even though we have tested upgrading the VM, some updates may render your VM inaccessible so please proceed only if you know what you are doing. If you run into problems, you can always re-init your VM or send us a request via [<EMAIL>](mailto:<EMAIL>).


### A few prep commands
To get started, log into your Koding account and check what version of the OS and Kernel that
you currently have by typing the following command in Terminal:
```
uname -rv
```
this should return you something like this:
```
3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:00:20 UTC 2014
```
Make a note of the kernel version, you can reference it later to ensure that the kernel update
worked.

You should also take a note of available disk space before you begin to ensure that you have adequate
space for all the updates. To get available disk space, type this command in Terminal:
{'fraction_non_alphanumeric': 0.06345514950166113, 'fraction_numerical': 0.016611295681063124, 'mean_word_length': 4.218370883882149, 'pattern_counts': {'":': 0, '<': 9, '<?xml version=': 0, '>': 16, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7228056', 'n_tokens_mistral': 870, 'n_tokens_neox': 793, 'n_words': 484}