Searches for Parrot tools on Ubuntu usually come from one of two places: someone who likes their current desktop and wants a few pentesting tools, or someone who read that you can “just add the Parrot repository” and is about to break their system. This guide covers both honestly. There are four workable ways to get Parrot Linux tooling onto Debian or Ubuntu, ranked from safest to riskiest, and one of them is a bad idea on Ubuntu no matter how many tutorials recommend it.
Everything here assumes you are testing systems you own or have written permission to test, or lab targets such as DVWA, Metasploitable, Hack The Box and TryHackMe. The tools are the same wherever you install them, and so are the legal rules.
First, understand what “Parrot tools” actually are
Parrot Linux is Debian underneath, with its own repository layered on top. Most of what people call Parrot tools fall into three groups:
- Plain Debian packages. nmap, Wireshark, John the Ripper, hashcat, sqlmap, nikto, aircrack-ng, hydra, gobuster, ffuf and dozens more exist in Debian’s and Ubuntu’s own repositories, sometimes a release or two behind.
- Parrot-packaged tools. Software Parrot builds itself because Debian does not ship it or ships it too old: Metasploit, Burp Suite Community, the
parrot-tools-*metapackages, AnonSurf and the Parrot application menu. - Parrot system pieces. The kernel, desktop theming, Firejail profiles, AppArmor tweaks and the
parrot-upgradewrapper. These are what make Parrot feel like Parrot, and they are exactly the pieces you do not want to mix into another distribution.
The Parrot vs Debian comparison explains that layering in more depth. Once you know which group a tool belongs to, choosing an install method is easy.
Method 1: Install Parrot tools on Ubuntu or Debian from your own repository (safest)
For the first group you do not need Parrot at all. On Ubuntu or Debian:
sudo apt update
sudo apt install nmap wireshark john hashcat sqlmap nikto aircrack-ng hydra gobuster ffuf netcat-openbsd whois dnsutilsDuring the Wireshark install, answer “Yes” when asked whether non-root users may capture packets, then add yourself to the group and log out and back in:
sudo usermod -aG wireshark $USERCheck versions with nmap --version and compare against the tool’s own site if you care about the latest features. On Ubuntu LTS the gap can be noticeable; on Debian 13 it is usually small, because Parrot 7.4 tracks the same Debian base.
A few popular tools are not in either repository and ship their own installers: Burp Suite Community comes as a Linux installer from PortSwigger, and Metasploit Framework is installed with Rapid7’s installer script, which sets up its own repository and PostgreSQL. Both work the same way on Ubuntu, Debian and Parrot, so the Metasploit setup guide and the Burp Suite guide on this site apply almost line for line.
This method keeps apt healthy, keeps security updates flowing from your own distribution and covers most of what a learner needs.
Method 2: Run Parrot in Docker (best for the full toolset)
If you want the actual Parrot environment, with its metapackages and the full menu of tools, without reinstalling your OS, the official Parrot container images are the cleanest answer. They are stock Parrot userspace running on your existing kernel. Install Docker from your distribution or from Docker’s own repository, then pull the image. The exact image names and tags are listed on the Parrot Docker images page; a typical session looks like this:
docker pull IMAGE_NAME
docker run -it --rm --name parrot IMAGE_NAME /bin/bash
# inside the container:
apt update && apt install nmapReplace IMAGE_NAME with the image you chose. Inside the container Parrot’s repository is already configured, so apt install parrot-tools-full or a smaller metapackage pulls in the same packages you would get on a real install. Two practical additions:
- Mount a working directory so your scan output survives: add
-v ~/labwork:/root/labworkto the run command. - For tools that need raw sockets or packet injection (nmap SYN scans, aircrack-ng), add
--cap-add=NET_RAW --cap-add=NET_ADMIN, or--network hostwhen you need to see your real interfaces. Wireless injection from inside a container still depends on the host driver and is rarely worth the trouble; use a VM or a real install for that.
Docker gives you no desktop, so GUI tools like Burp or Wireshark are awkward. For command-line work, which is most of the Parrot toolset, it is ideal, and you can throw the container away and start clean whenever you like. The general Docker usage doc covers persistent containers and updating the image.
Method 3: Run Parrot in a virtual machine or WSL
A VM gives you the complete Parrot experience, desktop included, isolated from your daily system. VirtualBox is in Ubuntu’s repository, and the VirtualBox install walkthrough covers the rest. Allocate at least 4 GB of RAM and 2 CPU cores for the Security Edition; the Home Edition is comfortable with less. On a Windows host, WSL 2 can run a Parrot root filesystem for command-line tools, though USB wireless adapters and GUI tools are easier in a full VM.
Choose a VM over Docker when you want Wireshark and Burp with a proper display, when you need wireless adapter passthrough, or when you want to snapshot the whole system before trying something destructive.
Method 4: Add the Parrot repository to your system (read this before you do it)
This is the method most tutorials jump to, and it needs a warning in bold: do not add the Parrot repository to Ubuntu. Ubuntu is not Debian. Its libc, Python, systemd and toolchain versions differ from Debian’s, and Parrot’s packages are built against Debian. Adding the repository usually looks fine until the next apt upgrade pulls in a Parrot build of a core library and leaves you with a system that will not boot, or a package manager that refuses every operation. The Debian community calls the result a “FrankenDebian”, and it is one of the most common ways to wreck an install.
On Debian 13 the picture is different, because Parrot 7.4 is built on the same base. It is still unsupported by both projects, but it can be done carefully if you pin the repository so that only packages you explicitly request come from Parrot. The pattern is:
- Import Parrot’s archive signing key into
/etc/apt/keyrings/. Get the key and the current repository line from the official site at parrot.sh rather than from a random blog; keys rotate and stale instructions are everywhere. - Add a sources file, for example
/etc/apt/sources.list.d/parrot.sources, pointing at a Parrot mirror for the release that matches Debian 13. The mirror guide explains how to pick a fast one. - Create
/etc/apt/preferences.d/parrotwith a low default priority for everything from Parrot, so nothing is pulled in automatically:
Package: *
Pin: origin "deb.parrot.sh"
Pin-Priority: 100Adjust the origin to the host used in your sources file. A priority below 500 means a Parrot package is never chosen over Debian’s unless you ask for it by name and version:
sudo apt update
apt policy metasploit-framework # shows the candidate from each origin
sudo apt install metasploit-framework=VERSION_SHOWNBefore any install, check what apt plans to pull in. apt install -s PACKAGE=VERSION simulates the operation; if the list includes core libraries such as libc6, systemd or python3 from the Parrot origin, stop. That package is not safe to take across. And never install parrot-core, the Parrot kernel metapackages or parrot-upgrade on a Debian system; those are system pieces, not tools.
Even done correctly, this is the method with the most ongoing maintenance: every Debian point release and every Parrot release is a chance for the pin to let something through. If you find yourself wanting more than three or four Parrot-only packages, Docker or a VM will serve you better.
Which method should you pick?
| You want | Use | Risk to your system |
|---|---|---|
| A handful of common tools | Method 1, your own repository | None |
| The full Parrot CLI toolset, disposable | Method 2, Docker | None |
| Parrot desktop, GUI tools, Wi-Fi adapters | Method 3, VM | None |
| One or two Parrot-only packages on Debian 13 | Method 4, pinned repository | Moderate, needs care |
| Parrot repository on Ubuntu | Do not | High, likely breakage |
If you keep reaching for the fourth row, it may be time to ask whether the right move is simply to install Parrot Linux. The dual boot guide for Parrot and Ubuntu lets you keep both, and the Parrot vs Ubuntu comparison helps you decide whether Parrot could replace Ubuntu outright.
Keeping the tools updated
With methods 1 and 4, updates arrive through the normal apt upgrade. With Docker, pull the image again and recreate your container; with a VM, run sudo parrot-upgrade inside it as you would on bare metal. Tools installed with vendor scripts (Metasploit, Burp) update through their own mechanisms, so include them in your routine rather than assuming apt covers them.
FAQ
Is there a single command to install all Parrot tools on Ubuntu?
No, and anything that promises one is adding the Parrot repository to Ubuntu, which is the one approach this guide tells you to avoid. Install individual tools from Ubuntu’s repository, or run the Parrot container image for the full set.
Will Ubuntu’s versions of nmap, sqlmap or hashcat be too old?
For learning and most lab work, no. If a specific feature is missing, most of these projects publish their own packages or build easily from source once build-essential is installed.
Can I get the Parrot menu and desktop on Ubuntu?
Not sensibly. The menu structure and theming are tied to Parrot’s own packages and desktop configuration. Use a VM, or install Parrot alongside Ubuntu.