注意:

The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.

Difference between revisions of "Docker"

From Funtoo
Jump to navigation Jump to search
 
Line 1: Line 1:
Funtoo is now uploading Dockerized stages to [https://hub.docker.com/u/funtoo our Docker Hub account]. Here's how to use them.
Funtoo is now uploading Dockerized stages to [https://hub.docker.com/u/funtoo our Docker Hub account]. For now we are dockerizing for Ryzen, Generic 64-bit and all the Intel CPUs Nehalem and up. Here's how to use them.


=== Setting up Docker ===
=== Setting up Docker ===

Latest revision as of 23:02, July 11, 2020

Funtoo is now uploading Dockerized stages to our Docker Hub account. For now we are dockerizing for Ryzen, Generic 64-bit and all the Intel CPUs Nehalem and up. Here's how to use them.

Setting up Docker

To set up docker on Funtoo Linux you will need to emerge app-emulation/docker, start up the docker startup script and ensure that your user is in the docker group.

Of course, you can use Funtoo docker images on any system that supports Docker -- it doesn't need to be Funtoo. If you're not using Funtoo, just ensure Docker is up and running then continue below.

Grabbing the image

To grab an image, pick the image you want and pull it:

user $ docker pull funtoo/stage3-intel64-skylake

Launching an Image

Since Funtoo docker images are set up to run OpenRC by default, you can simply start them in the background and will continue to run. Run an image in the background with the -d option:

user $ docker run -d funtoo/stage3-intel64-skylake

Entering an Image

To enter a bash shell inside the image, use docker ps to grab the CONTAINER ID and then specify it with the following docker exec command:

user $ docker exec -it ba1f3755fa03 /bin/bash
root #

Now that you are in the container, you should run an initial ego sync and perform any other tasks you want. You may want to create a user and set up your container so you can ssh into it directly:

root # ego sync

Exit the container shell as you normally would exit a shell, and you will be out of the container and back on your host.