parrotsec/core

Sponsored OSS

By ParrotSec

Updated about 5 hours ago

Official Base Image of Parrot OS

Image
Security
Operating systems
18

100K+

parrotsec/core repository overview

parrotsec/core

Core system with just the Parrot basics.

You can use it as a start point to create your custom containers.

example usage:

docker run --rm -ti --network host -v $PWD/work:/work parrotsec/core

Read More

Official Documentation

General Usage Instructions and Examples

Launch a container:

docker run --name pcore-1 -ti parrotsec/core

NOTE: the pcore-1 name is arbitrary and can be customized

Stop the container:

docker stop pcore-1

Resume a previously-stopped container:

docker start pcore-1

Remove a container after use:

docker rm pcore-1

List all the instantiated containers:

docker ps -a

Remove all the containers:

docker rm $(docker ps -qa)

Start a container and automatically remove it on exit:

docker run --rm -ti parrotsec/core

Use Volumes to share files with the host:

It is a good practice to not keep persistent Docker containers, but to remove them on every use and make sure to save important files on a Docker volume.

The following command creates a work folder inside the current directory and mounts it in /work inside the container.

docker run --rm -ti -v $PWD/work:/work parrotsec/core

Open a port from the container to the host

Every docker container has its own network space connected to a virtual LAN.

All the traffic from within the docker container will be NATted by the host computer.

If you need to expose a port to other machines outside your local computer, use the following exaple:

docker run --rm -p 8080:80 -ti parrotsec/core

Note that the first port is the port that will be opened on your host, and the second one is the container port to bind to.

Here a reference usage of the -p flag:

-p : -p 8080:80

-p :/ -p 8080:80/tcp

-p

:: -p 192.168.1.30:8080:80 (in case of multiple adresses on host network)

Use network host instead of docker NAT

Every docker container has its own network space connected to a virtual LAN.

All the traffic from within the docker container will be NATted by the host computer.

If you need to make the docker container share the same networking space of the host machine, then use the --network host flag as shown below

docker run --rm --network host -ti parrotsec/core

NOTE 1: every port opened in the container will be opened on the host as well.

NOTE 2: you can perform packet sniffing on the host network.

NOTE 3: iptables rules applied inside the container will take effect on the host as well.

Tag summary

Content type

Image

Digest

sha256:eb82578db

Size

179.4 MB

Last updated

about 5 hours ago

docker pull parrotsec/core

This week's pulls

Pulls:

763

Last week