The memory cgroup is not enabled
  • 31-May-2023
Lightrun Team
Author Lightrun Team
The memory cgroup is not enabled

The memory cgroup is not enabled.

Lightrun Team
Lightrun Team

Explanation of the problem

The user describes their attempt to enable memory cgroup in a Kubernetes cluster by appending cgroup_enable=memory cgroup_memory=1 to the cmdline.txt file in each node of the cluster. They mention that they have rebooted the nodes after making this modification. However, they report that the desired functionality is not working, indicating that the memory cgroup is not properly enabled.

The user provides the output of the microk8s inspect command, which displays the status and configuration details of various components and services in the Kubernetes cluster. Within the inspection report, a warning message is highlighted, indicating that the memory cgroup is not enabled. The warning suggests that the cluster may not be functioning properly due to the absence of cgroups. Additionally, a link to the MicroK8s documentation is provided as a reference for enabling cgroups, pointing the user to alternative installation options for ARM architectures.

Based on the information provided, it appears that enabling memory cgroup in the Kubernetes cluster is a critical step for its proper functioning. The user’s attempt to enable it by modifying the cmdline.txt file did not yield the expected results. To resolve the issue, the user is advised to follow the instructions provided in the MicroK8s documentation referenced in the warning message. By ensuring that cgroups are enabled as per the recommended guidelines, the cluster should be able to function correctly. If further assistance is required, it is recommended to consult the MicroK8s community or seek additional documentation specific to the cluster setup and environment.

Troubleshooting with the Lightrun Developer Observability Platform

Getting a sense of what’s actually happening inside a live application is a frustrating experience, one that relies mostly on querying and observing whatever logs were written during development.
Lightrun is a Developer Observability Platform, allowing developers to add telemetry to live applications in real-time, on-demand, and right from the IDE.

  • Instantly add logs to, set metrics in, and take snapshots of live applications
  • Insights delivered straight to your IDE or CLI
  • Works where you do: dev, QA, staging, CI/CD, and production

Start for free today

Problem solution for The memory cgroup is not enabled.

One of the answers suggests modifying the GRUB configuration by adding specific parameters to the GRUB_CMDLINE_LINUX variable. The user recommends including the following values: cgroup_enable=memory, cgroup_memory=1, and systemd.unified_cgroup_hierarchy=0. It is indicated that all three parameters are necessary for enabling the memory cgroup functionality.

Another answer provides a solution specifically for Ubuntu 22.04. The user advises opening the /etc/default/grub file and locating the line where the GRUB_CMDLINE_LINUX string is set. They suggest adding cgroup_enable=memory cgroup_memory=1 to the existing string. After saving the file, the user should run sudo update-grub. They also share an example of how the modified GRUB_CMDLINE_LINUX line should look like in their case.

In conclusion, the recommended approach to enable memory cgroup involves modifying the GRUB configuration file. This can be achieved by adding the necessary parameters to the GRUB_CMDLINE_LINUX line. The exact parameters may vary depending on the specific requirements of the system, but typically include cgroup_enable=memory and cgroup_memory=1. Once the modifications are made, it is essential to save the file and update the GRUB configuration using the appropriate command (sudo update-grub). By following these steps and rebooting the system, the memory cgroup functionality should be enabled, as confirmed by running the microk8s.inspect command.

Other popular problems with canonical microk8s

Problem: “The connection to the server was refused – did you specify the right host or port?” error message

This error message indicates that the connection to the Kubernetes API server has been refused, likely due to a problem with the Kubernetes API server itself or a misconfiguration of the MicroK8s installation.


One possible solution is to check the status of the MicroK8s service by running the command sudo microk8s status --wait-ready. If the service is not running, start it with the command sudo systemctl start snap.microk8s.daemon-kubelet.service. If the problem persists, you may need to uninstall and reinstall MicroK8s.

Problem: Difficulty accessing the Kubernetes dashboard

MicroK8s includes a built-in Kubernetes dashboard that can be accessed through a web browser. However, some users may encounter difficulty accessing the dashboard, either due to a problem with the dashboard itself or a network configuration issue.


One possible solution is to ensure that the correct ports are open for accessing the dashboard. By default, the dashboard can be accessed at https://<node-ip>:10443/. Ensure that port 10443 is open on the node running MicroK8s. If the problem persists, you may need to re-install the dashboard by running the command microk8s enable dashboard.

Problem: Issues with pod networking

MicroK8s uses a containerd runtime to manage pod networking, which can sometimes result in networking issues. One common problem is that the containers in the pods cannot communicate with each other, either because they are not on the same network or because of a misconfiguration.


One possible solution is to check the network policies in the Kubernetes cluster by running the command microk8s kubectl get networkpolicies. If there are no network policies, you may need to create one using the microk8s kubectl create command. Another possible solution is to ensure that the pod network is properly configured by checking the MicroK8s configuration file at /var/snap/microk8s/current/args/containerd-template.toml and making any necessary modifications.

A brief introduction to canonical microk8s

Canonical microk8s is a lightweight, fast, and simplified Kubernetes distribution designed for small-scale deployments, local development, and edge computing. It provides a complete and secure Kubernetes environment with all the necessary components, including the Kubernetes API server, etcd, kubelet, and other essential add-ons like Prometheus, Grafana, and Istio. Unlike other Kubernetes distributions, microk8s is packaged as a single snap package and can be installed and run on any Linux distribution without any additional dependencies. This makes it an excellent choice for developers, hobbyists, and small businesses looking for an easy-to-use and efficient Kubernetes platform.

Microk8s is built with simplicity and speed in mind. It includes a simplified Kubernetes command-line interface (CLI) that allows users to easily deploy, scale, and manage Kubernetes applications. It also includes a range of add-ons and plug-ins that are installed and configured by default, making it easy to get started with Kubernetes development without having to deal with complex installation and configuration processes. With microk8s, users can spin up a complete Kubernetes environment in just a few seconds, making it a great choice for local development and testing of Kubernetes applications. Additionally, microk8s provides a range of security features, including container isolation, network policies, and role-based access control, ensuring that users can deploy and manage Kubernetes applications with the utmost confidence.

Most popular use cases for canonical microk8s

  1. Container Orchestration: Canonical MicroK8s is a lightweight, self-contained Kubernetes distribution designed for developers and IoT use cases. It can be used to orchestrate containers in production or development environments with minimal overhead, making it ideal for small-scale projects that require efficient management of microservices.
  2. Local Development and Testing: MicroK8s provides a local development environment for Kubernetes, enabling developers to create, test, and debug their applications in a containerized environment without requiring a full-blown Kubernetes cluster. With MicroK8s, developers can create a cluster in a matter of minutes, deploy their code, and test it locally before deploying to a production environment.
  3. Integration with Other Technologies: MicroK8s is a versatile technology that can be integrated with other open-source tools and technologies to build complex applications. For example, you can use MicroK8s with Istio to manage microservices, or with Prometheus to monitor your Kubernetes cluster. Here’s an example of deploying a simple NGINX web server using MicroK8s:
apiVersion: v1
kind: Pod
  name: nginx
    - name: nginx
      image: nginx:latest
        - containerPort: 80

This YAML manifest defines a Kubernetes Pod with a single container running the latest version of the NGINX web server. The container listens on port 80, which is exposed by the Pod. You can deploy this manifest to your MicroK8s cluster using the kubectl apply command, and then access the web server using the IP address of the Pod.


It’s Really not that Complicated.

You can actually understand what’s going on inside your live applications.

Try Lightrun’s Playground

Lets Talk!

Looking for more information about Lightrun and debugging?
We’d love to hear from you!
Drop us a line and we’ll get back to you shortly.

By submitting this form, I agree to Lightrun’s Privacy Policy and Terms of Use.