EECS Technical Database

User Tools

Site Tools

You are here: Technical Database » Departmental Services » Podman/Docker
Trace:
services:podman

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
services:podman [2024/12/19 14:23] – jasservices:podman [2025/04/02 13:43] (current) – jas
Line 1: Line 1:
 ====== Podman/Docker ====== ====== Podman/Docker ======
  
-Podman (short for pod manager) is an open source tool for developing, managing, and running containers. It was developed by Red Hat engineers along with the open source community.  Docker is also an open platform for developing, shipping, and running applications. +Podman (short for Pod Manager) is an open source tool for developing, managing, and running containers. It was developed by Red Hat engineers along with the open source community.  Docker is also an open platform for developing, shipping, and running applications. 
  
-EECS Linux systems run a Red Hat Enterprise Linux compatible operating system.  Podman is installed by default. As a result, Podman is the only supported container environment on EECS tech supported systems.+EECS Linux systems run a Red Hat Enterprise Linux compatible operating system called Rocky Enterprise Linux.  Podman is installed by default.  Podman is the only supported container environment on EECS tech supported systems.
  
 Fortunately, both Podman and Docker support the same image format, so you can generally use Docker images with Podman and vice versa. Images built with Docker-specific features might require minor adjustments to work with Podman.  Fortunately, both Podman and Docker support the same image format, so you can generally use Docker images with Podman and vice versa. Images built with Docker-specific features might require minor adjustments to work with Podman. 
Line 11: Line 11:
 1) Request permission to use Podman by sending an email to tech.  Please include your research group, and the server name where you would like to use containers.  Tech will allocate a uniqe uid/gid range for your containers. 1) Request permission to use Podman by sending an email to tech.  Please include your research group, and the server name where you would like to use containers.  Tech will allocate a uniqe uid/gid range for your containers.
  
-2) By default, Podman will use your EECS home directory for container storage ($HOME/.local/share/containers/storage). Your home directory is a network share which is not supported for container storage.  Configure Podman to use storage that is **local** to the server (eg. /local/home/<user>).  Here's how you will configure that:+2) By default, Podman will use your EECS home directory for container storage ($HOME/.local/share/containers/storage). Your home directory is a network share which is not supported for container storage.  It also has limited storage space.  Configure Podman to use storage that is **local** to the server (eg. /local/home/<user>).  Here's how you will configure that:
  
 a) Get rid of any old Podman configuration in your account: a) Get rid of any old Podman configuration in your account:
Line 42: Line 42:
  
 Of course, replace <user> with your username. Of course, replace <user> with your username.
 +
 +NOTE: For temporary purposes, you can also specify the container storage location on the command to the podman command instead of configuring it as above:
 +
 +  podman --root /tmp/<user>/storage --runroot /tmp/<user>/runstorage <command>
  
 3) Now you can test container storage: 3) Now you can test container storage:
services/podman.txt · Last modified: by jas