Skip to main content

Create a Docker Container in the Host network

 

#Start a new container - which has the same ip as Host Container
docker run -it --network host kalilinux/kali-rolling

#Start a container 
docker start Container_ID

#Attach a container 
docker attach Container_ID
ctrl+p & ctrl+q to detach from a container without killing it 

#Start a container in Detached mode
docker run -d --network host kalilinux/kali-rolling

#Start a container in bridge network 
#Default is bridge network
docker run -dit --name test kalilinux/kali-rolling /bin/bash

Bridge network = new Docker network - separate network
Host = Docker Host network 

#Create a bridge network
docker network create --driver=bridge my_bridge_network --subnet=10.10.10.0/24 --gateway=10.10.10.1

#Run the container in Bridge network 
docker run -it --name my_container --network my_bridge_network --ip 10.10.10.2 ubuntu:latest
Moving Docker Container to a Different Host 

#list the containers and copy the id
docker container ls 

#stop the container
docker stop <Container_ID_or_name>

#Create a new image 
docker commit <container_ID> <new_name:tag>

#save the image to a tar file to export
docker save -o <container_backup.tar> <Image_name>

#Push the container to a new Host
scp <container_backup.tar> root@10.10.10.10:/home/backup/

#Login to the new host and load the container, might take some time based on the container size
docker load -i <container_backup.tar>

#List the images, confirm your new docker container here 
docker images

#Create/run the container 
docker create --name kali container_backup
docker container container_id start
or
#create and start the container docker run -it --name kali --hostname kali <Image_id> #Setup auto restart docker update --restart unless-stopped kali #Verify restart status docker inspect -f '{{.HostConfig.RestartPolicy.Name}}' kali #make sure docker starts on boot sudo systemctl enable docker
Basic Docker Commands

#list containers
sudo docker ps 

#Get a shell 
docker exec -it <container_name_or_id> /bin/bash



Comments

Popular posts from this blog

Pivoting into an internal network behind firewall

    Accessing a Victim network from Windows box which is pivoted to Kali #On Kali sshuttle --listen 0.0.0.0 -r user@10.10.10.10 192.168.1.0/24 or ./chisel server --port 9001 -reverse #On Victim ./chisel.exe client 10.10.10.1:9001 R:0.0.0.0:1080:socks .\chisel.exe client 10.10.10.1:9001 R:8080:127.0.0.1:8080 R:8888:127.0.0.1:8888 R:9090:127.0.0.1:9090 #On windows route print #delete default route route delete 0.0.0.0 #add a new route to kali- setting kali ip as gateway; kali_ip=which is on the same subnet as the windows box route add 0.0.0.0 mask 0.0.0.0 KALI_IP #Now you should be able to access all the sites which are accessible on kali from windows box. #If the above doesnt work #asuming Kali and windows are on Eht0 #add a firewall rule to allow Kali ip traffic netsh advfirewall firewall add rule name="Allow VPN Traffic" dir=in action=allow protocol=any remoteip=KALI_ETH0_IP #on Kali - Allow tun0 traffic to forward on iptables sudo iptables -P FORWARD ACCEPT ...