>>FIRST MISSION//LOGS//containers//disable-snap-daemon-in-archlinux.MD
[ + ] TARGET_LOCKED200 OK
JAN 24, 2019timer 3 MIN READSYS_TAG: containers STATUS: VERIFIED_WORKING

Disable Snap Daemon in Archlinux

ENGINE: KERNEL // STABLE
BASE_ARCH: x86_64
HOST: VASTORIGINS.COM
GPG: OKSIG_ID: 0x4EB27DB0

Carry out a random act of kindness, with no expectation of reward, safe in the knowledge that one day someone might do the same for you.

~ Princess Diana.

One day I woke up and I just didn’t want to use Snap apps anymore. It was not a dramatic moment, just a quiet realization that several services were running in the background of my workstation for a package system I was not using, and every boot was spending time and memory on them. So how do I remove it from my workstation? Here are the things I did to completely remove it from my workstation.

🔍 Find What’s Running

In order to disable Snap apps on your workstation you must first list all snap services and the included PID (Process Identifier) sockets running:

systemctl list-unit-files | grep snap

The output will show you every systemd unit that Snap installed, from the main daemon to the mount units that handle the loop devices Snap uses to distribute its apps. A few of them are enough; the list can get long.

⛔ Disable the Services

After you listed all of it, you must disable all known snap services. Below is just a gist of running snap services on my workstation (on Fedora Linux):

sudo systemctl disable snapd.service  
sudo systemctl disable snapd.seeded.service  
sudo systemctl disable snapd.socket  
sudo systemctl disable var-lib-snapd-snap-core-6130.mount

Each disable command tells systemd not to start that unit at boot. The socket unit is the sneaky one: even if the daemon is disabled, a socket can still wake it up on demand, so disabling it too is what makes the removal actually stick.

After you completed the steps above you must then restart your workstation for a much cleaner startup. On the next boot, no snap processes, no snap mounts, and no surprises in your service list.

🧠 Final Thoughts

So guys, if you have any problem running the above commands let me know. Removing a package system you do not use is one of those small cleanups that makes your machine feel lighter, even if the only measurable difference is a shorter boot log. That’s it guys, as always live life and hope you enjoyed this article!

[ SIGNATURE VERIFIED // GPG 0x4EB27DB0 // PROVENANCE SECURE ]
➔ RETURN TO LOGS