From 39d169e975333ec3f921b577248eb5f965d5f8e8 Mon Sep 17 00:00:00 2001
From: tiyn <tiyn@posteo.eu>
Date: Sat, 21 Feb 2026 18:21:49 +0100
Subject: [PATCH] proxmox: added balooning errors

---
 wiki/linux/proxmox.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/wiki/linux/proxmox.md b/wiki/linux/proxmox.md
index 22e7836..f1b5a5e 100644
--- a/wiki/linux/proxmox.md
+++ b/wiki/linux/proxmox.md
@@ -194,3 +194,16 @@ Find them with `find /etc -change '*eth0*'` and move them to the new name.
 After that `reboot` and the internet should be up again.
 (sources: [debian website](https://wiki.debian.org/NetworkInterfaceNames) and
 [proxmox forum](https://forum.proxmox.com/threads/upgrade-motherboard-reinstall.48630))
+
+### Balooning RAM and Resulting Problems
+
+When using a balooning device for RAM error messages - for example by [Docker](/wiki/docker.md) can
+be hidden.
+It is then more difficult to find the out-of-memory error that makes a program crash.
+Problems with balooning RAM can be found using the following command.
+
+```sh 
+journalctl -k
+```
+
+A typical error message for this type of issue is `Out of puff!`.