From Fedora Project Wiki
No edit summary |
No edit summary |
||
(7 intermediate revisions by the same user not shown) | |||
Line 3: | Line 3: | ||
Download and run a Docker image with Cockpit | Download and run a Docker image with Cockpit | ||
|setup= | |setup= | ||
Log into Cockpit. | |||
Make sure that Docker is active by following these steps inside Cockpit: | |||
# Navigate to "Services" page. | |||
# Switch to the "Sockets" tab. | |||
# Find the "docker.socket" unit and start it if neccessary. | |||
# Optionally, you can also "enable" the unit so that it starts after every boot. | |||
Alternatively, you can run these commands in a shell: | |||
<pre> | |||
# systemctl start docker.socket | |||
# systemctl enable docker.socket | |||
</pre> | |||
|actions= | |actions= | ||
# Navigate to the "Containers" page. | # Navigate to the "Containers" page. | ||
# Download the "fedora" image. | # Download the "fedora" image. | ||
# Create a new container by running the image. | # Create a new container by running the image. Use <code>/bin/bash</code> as the command and make sure it has a terminal. | ||
# Type some commands into the container terminal. | # Type some commands into the container terminal. Maybe <code>yum update</code>. | ||
# Monitor the memory and CPU usage of the container. | |||
|results= | |results= | ||
No errors should occur. | No errors should occur. | ||
}} | }} |
Latest revision as of 09:56, 23 March 2015
Description
Download and run a Docker image with Cockpit
Setup
Log into Cockpit.
Make sure that Docker is active by following these steps inside Cockpit:
- Navigate to "Services" page.
- Switch to the "Sockets" tab.
- Find the "docker.socket" unit and start it if neccessary.
- Optionally, you can also "enable" the unit so that it starts after every boot.
Alternatively, you can run these commands in a shell:
# systemctl start docker.socket # systemctl enable docker.socket
How to test
- Navigate to the "Containers" page.
- Download the "fedora" image.
- Create a new container by running the image. Use
/bin/bash
as the command and make sure it has a terminal. - Type some commands into the container terminal. Maybe
yum update
. - Monitor the memory and CPU usage of the container.
Expected Results
No errors should occur.