document/TranslateProject
2
0
Fork 0
mirror of https://github.com/LCTT/TranslateProject.git synced 2024-12-26 21:30:55 +08:00
Code Issues Packages Projects Releases Wiki Activity

清理文章内容

Browse Source
This commit is contained in:
lkxed 2022-05-23 18:13:34 +08:00
parent e3ffa65be1
commit 3464557a10
1 changed files with 5 additions and 33 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
sources/tech/20220523 A hands-on guide to images and containers for developers.md
View File

@ -69,8 +69,6 @@ These are a sampling of different image registries available on the internet:
There are two utilities whose purpose is to manage images and containers: [Docker][8]and [Podman][9]. They are available for Windows, Linux, and Mac workstations. From a developer's point of view, they are completely equivalent when executing commands. They can be considered aliases of one another. You can even install a package on many systems that will automatically change Docker into a Podman alias. Wherever Podman is mentioned in this document, Docker can be safely substituted with no change in outcome.
[ Read next: 5 underused Podman features to try now ]
You'll immediately notice these utilities are very similar to [Git][10] in that they perform tagging, pushing, and pulling. You will use or refer to this functionality regularly. They should not be confused with Git, however, since Git also manages version control, whereas images are immutable and their management utilities and registry have no concept of change management. If you push two images with the same name and tag to the same repository, the second image will overwrite the first with no way to see or understand what has changed.
#### Subcommands
@ -78,33 +76,17 @@ You'll immediately notice these utilities are very similar to [Git][10] in that
The following are a sampling of Podman and Docker subcommands you will commonly use or refer to:
* build: `build` an image
Example: `podman build -t org/some-image-repo -f Dockerfile`
* Example: `podman build -t org/some-image-repo -f Dockerfile`
* image: manage `image`s locally
Example: `podman image rm -a` will remove all local images.
* Example: `podman image rm -a` will remove all local images.
* images: list `images` stored locally
* tag: `tag` an image
* container: manage `container`s
Example: `podman container rm -a` will remove all stopped local containers.
* Example: `podman container rm -a` will remove all stopped local containers.
* run: `create` and `start` a container
also `stop` and `restart`
* also `stop` and `restart`
* pull/push: `pull`/push and image from/to a repository on a registry
* Example: `podman build -t org/some-image-repo -f Dockerfile`
* Example: `podman image rm -a` will remove all local images.
* Example: `podman container rm -a` will remove all stopped local containers.
* also `stop` and `restart`
#### Dockerfiles
Dockerfiles are the source files that define images and are processed with the `build` subcommand. They will define a parent or base image, copy in or install any extra software you want to have available to run in your image, define any extra metadata to be used during the build and/or runtime, and potentially specify a command to run when a container defined by your image is run. A more detailed description of the anatomy of a Dockerfile and some of the more common commands used in them is in the lab below. A link to the complete Dockerfile reference appears at the end of this article.
@ -393,16 +375,6 @@ This article introduces four key ideas for software developers new to images and
3. "Build once, deploy many": This principle is what makes container technology so useful. Images and containers provide consistency in deployments and independence from the host machine, allowing you to deploy with confidence across many different environments. Containers are also easily scalable because of this principle.
4. Externalize the configuration: If your image has configuration data that is environment-specific, release-independent, or secret, consider making that data external to the image and containers. You can inject this data into your running image by injecting an environment variable or mounting an external file into the container.
### Additional reading
[A brief history of containers: from the 1970s till now][16]
[A practical introduction to container terminology][17]
[Dockerfile reference][18]
[Podman vs. Docker][19]
--------------------------------------------------------------------------------
via: https://opensource.com/article/22/5/guide-containers-images