---
title: Strict MicroK8s
description: Canonical makes open source secure, reliable and easy to use, providing
  support for Ubuntu and a portfolio of enterprise-grade technologies. Founded in
  2004, Canonical operates globally with team members in over 80 countries.
url: https://canonical.com/microk8s/docs/install-strict?format=md
---

*Submit*

# Strict MicroK8s

Before you install the strictly confined version of MicroK8s, please familiarise yourself with the differences by reading this [explanation of strict confinement](https://canonical.com/microk8s/docs/strict-confinement).

## [Install strict](https://canonical.com/microk8s/docs/install-strict?format=md#p-36102-install-strict)

Strictly confined MicroK8s is installed via the tracks that include strict in their name. For example:

```
snap install microk8s --channel 1.29-strict
```

If there are workloads that don’t run as expected under strict confinement Apparmor denials will be reported in the system logs. You can try to find what is causing the problem by using [snappy-debug](https://snapcraft.io/docs/debug-snaps).

You can also try running the snap in devmode. A devmode snap runs as a strictly confined snap with full access to system resources and produces debug output to identify unspecified interfaces. You need to install the snap with the devmode flag:

```
snap install microk8s --channel=1.29-strict --devmode
```

Last updated 2 years ago. [Help improve this document in the forum](https://discuss.kubernetes.io/t/strict-microk8s/21487).