《Docker实战》授权指南：2016版

docker
需积分: 11 3 下载量 11 浏览量 更新于2024-07-20 收藏 8.84MB PDF 举报
《Docker in Action: 2016版》是一本由Jeff Nickoloff编写的实践指南，专为理解和应用Docker容器技术而设计。本书针对的是那些希望深入了解Docker如何简化软件开发、部署和运维的专业人士。Manning出版社出版，封面注明版权信息，强调了版权保护并规定了复制或传播的条件。 在本书中，读者将学到一系列关键知识点，包括但不限于： 1. **Docker基础知识**：章节将从Docker的基本概念出发，介绍什么是容器，为何选择Docker而非传统的虚拟机（VM），以及其核心原理，如镜像（Images）和容器（Containers）的创建与管理。 2. **Dockerfile编写**：学习如何通过Dockerfile自定义镜像，这是一种文本文件，用于指示如何构建和运行一个Docker容器。这涉及基础指令和最佳实践，确保可重复性和一致性。 3. **容器网络与通信**：探讨Docker网络模型，如桥接网络、主机网络模式和自定义网络，以及如何设置端口映射，实现服务间的通信。 4. **Docker Compose与Kubernetes**：深入理解如何使用Docker Compose进行多容器应用的配置和管理，以及如何将应用扩展到大规模场景，如 Kubernetes，以便在生产环境中实现自动化部署和扩展。 5. **Docker安全与最佳实践**：讨论如何保障Docker环境的安全性，包括镜像的安全构建、权限管理和网络隔离策略。 6. **微服务与容器化**：介绍微服务架构的优势，并展示如何通过Docker优化微服务的部署和运维。 7. **Docker容器生命周期管理**：学会如何使用Docker命令行工具（如docker run、docker ps、docker stop等）以及Docker Hub、Registry等服务进行容器的生命周期管理。 8. **实战案例分析**：书中包含丰富的实战项目，让读者在实际操作中加深对Docker的理解，解决常见问题并提升技能。 此外，书中的资源还提供了Manning出版社的购买链接和折扣信息，以及版权声明和联系方式，以便读者寻求更多相关资料或获取授权复制信息。 《Docker in Action: 2016版》是一本实用且深入的教程，无论是初学者还是有经验的开发者，都能从中受益匪浅，掌握Docker这一现代IT领域的核心技术。

Docker in Action

2018-03-14 上传
Docker in Action teaches readers how to create, deploy, and manage applications hosted in Docker containers. After starting with a clear explanation of the Docker model, you will learn how to package applications in containers, including techniques for testing and distributing applications. You will also learn how to run programs securely and how to manage shared resources. Using carefully designed examples, the book teaches you how to orchestrate containers and applications from installation to removal. Along the way, you'll discover techniques for using Docker on systems ranging from dev-and-test machines to full-scale cloud deployments.

Docker in action

2018-11-04 上传
Docker in Action starts with a clear explanation of the Docker model of virtualization and shows how to create, deploy, and manage applications hosted in Docker containers. It offers specific techniques for testing and distributing applications via Docker Hub and other registries. It shows how to take advantage of the Linux OS features that Docker uses to run programs securely, and how to manage shared resources. Using carefully-designed examples, the book guides readers on orchestrating containers and applications from installation to removal. Along the way, it teaches techniques for using Docker on systems ranging from personal dev-and-test machine to full-scale cloud deployments.

Docker-in-Action.pdf

2018-04-04 上传
Docker-in-Action.pdf In 2011, I started working at Amazon.com. In that first week my life was changed as I learned how to use their internal build, dependency modeling, and deployment tool- ing. This was the kind of automated management I had always known was possible but had never seen. I was coming from a team that would deploy quarterly and take 10 hours to do so. At Amazon I was watching rolling deployments push changes I had made earlier that day to hundreds of machines spread all over the globe. If big tech firms had an engineering advantage over the rest of the corporate landscape, this was it. Early in 2013, I wanted to work with Graphite (a metrics collection and graphing suite). One day I sat down to install the software and start integrating a personal proj- ect. At this point I had several years of experience working with open source applica- tions, but few were as dependent on such large swaths of the Python ecosystem. The installation instructions were long and murky. Over the next several hours, I discov- ered many undocumented installation steps. These were things that might have been more obvious to a person with deeper Python ecosystem knowledge. After pouring over several installation guides, reading through configuration files, and fighting an epic battle through the deepest parts of dependency hell, I threw in the towel. Those had been some of the least inspiring hours of my life. I wanted nothing to do with the project. To make matters worse, I had altered my environment in a way that was incompatible with other software that I use regularly. Reverting those changes took an embarrassingly long time. I distinctly remember sitting at my desk one day in May that year. I was between tasks when I decided to check Hacker News for new ways to grow my skillset. Articles about a technology called Docker had made the front page a few times that week. That evening I decided to check it out. I hit the site and had the software installed within a few minutes. I was running Ubuntu on my desktop at home, and Docker only had two dependencies: LXC and the Linux kernel itself. Licensed to Stephanie Bernal <nordicka.n@gmail.com> PREFACE xiv Like everyone else, I kicked the tires with a “Hello, World” example, but learned little. Next I fired up Memcached. It was downloaded and running in under a minute. Then I started WordPress, which came bundled with its own M y SQL server. I pulled a couple different Java images, and then Python images. Then my mind flashed back to that terrible day with Graphite. I popped over to the Docker Index (this was before Docker Hub) and did a quick search. The results came back, and there it was. Some random user had created a Graphite image. I pulled it down and created a new container. It was running. A simple but fully configured Graphite server was running on my machine. I had accomplished in less than a minute of download time what I had failed to do with several hours a few months earlier. Docker was able to demonstrate value with the simplest of examples and minimum effort. I was sold. Over the next week, I tried the patience of a close friend by struggling to direct our conversations toward Docker and containers. I explained how package management was nice, but enforcing file system isolation as a default solved several management problems. I rattled on about resource efficiency and provisioning latency. I repeated this conversation with several other colleagues and fumbled through the container story. Everyone had the same set of tired questions, “Oh, it’s like virtualization?” and “Why do I need this if I have virtual machines?” The more questions people asked, the more I wanted to know. Based on the popularity of the project, this is a story shared by many. I began including sessions about Docker when I spoke publicly. In 2013 and 2014, only a few people had heard of Docker, and even fewer had actually tried the software. For the most part, the crowds consisted of a few skeptical system administrator types and a substantial number of excited developers. People reacted in a multitude of ways. Some were pure rejectionists who clearly preferred the status quo. Others could see problems that they experienced daily solved in a matter of moments. Those peo- ple reacted with an excitement similar to mine. In the summer of 2014, an associate publisher with Manning called me to talk about Docker. After a bit more than an hour on the phone he asked me if there was enough content there for a book. I suggested that there was enough for a few books. He asked me if I was interested in writing it, and I became more excited than I had been for some time. That fall I left Amazon.com and started work on Docker in Action. Today, I'm sitting in front of the finished manuscript. My goal in writing this book was to create something that would help people of mixed backgrounds get up to speed on Docker as quickly as possible, but in such a way that they understand the underlying mechanisms. The hope is that with that knowledge, readers can under- stand how Docker has been applied to certain problems, and how they might apply it in their own use-cases.

#!/bin/bash #Author: 柠檬班可优 #Date: 2019-06-06 #install docker in ubuntu and centos function install_docker_in_ubuntu { sudo apt-get update -y # install some tools sudo apt-get install \ apt-transport-https \ ca-certificates \ curl \ gnupg-agent \ software-properties-common \ net-tools \ wget -y # install docker curl -fsSL get.docker.com -o get-docker.sh sh get-docker.sh # start docker service sudo groupadd docker &> /dev/null sudo gpasswd -a "${USER}" docker sudo systemctl start docker rm -rf get-docker.sh } function install_docker_in_centos { # install some tools sudo yum install -y git vim gcc glibc-static telnet bridge-utils # install docker curl -fsSL get.docker.com -o get-docker.sh sh get-docker.sh # start docker service sudo groupadd docker &> /dev/null sudo gpasswd -a "${USER}" docker sudo systemctl start docker rm -rf get-docker.sh } SYSTEM_NAME="$(awk -F= '/^NAME/{print $2}' /etc/os-release)" if [[ "${SYSTEM_NAME,,}" =~ "ubuntu" ]] ; then echo "Your system is ubuntu." echo "Installing Docker in ubuntu..." install_docker_in_ubuntu elif [[ "${SYSTEM_NAME,,}" =~ "centos" ]] ; then echo "Your system is centos." echo "Installing Docker in centos..." install_docker_in_centos else echo "This script can only run in ubuntu and centos system." exit 1 fi

2023-06-06 上传
代码中定义了两个函数 `install_docker_in_ubuntu` 和 `install_docker_in_centos`，分别用来在 Ubuntu 和 CentOS 系统中安装 Docker。在主函数中，通过检查系统名称来确定是在 Ubuntu 还是 CentOS 系统中运行脚本，...

docker与微服务实战2022 docker_boot.jar 下载

2023-07-07 上传
要下载docker_boot.jar文件，您可以按照以下步骤进行实战： 1. 首先确保您已经安装了Docker，并且具备运行Docker命令的权限。 2. 打开终端或命令提示符，执行以下命令来搜索docker_boot.jar文件是否可用： ``` ...

run_docker_rcall.sh: 171: run_docker_rcall.sh: Syntax error: "(" unexpected

2023-07-14 上传
这个错误通常表示 `run_docker_rcall.sh` 脚本中存在语法错误，可能是由于脚本版本不兼容或脚本本身存在问题引起的。 要解决此问题，您可以尝试以下几个步骤： 1. 确认您使用的是正确的脚本版本。检查脚本的来源，...

sonic-buildimage 编译怎么使用SONIC_DOCKER_IMAGES，举个例子

2023-05-30 上传
使用SONIC_DOCKER_IMAGES变量来指定构建SONiC时所需的Docker镜像非常简单。下面是一个例子： 假设你需要在SONiC中使用Redis数据库，可以按照以下步骤进行操作： 1. 打开sonic-buildimage目录下的Makefile文件。 2...

prometheus使用 docker_sd_config 监控docker集群

2023-05-31 上传
要使用 `docker_sd_config` 监控 Docker 集群，需要在 Prometheus 的配置文件中设置相应的服务发现规则。以下是一个示例配置文件，用于监控运行在 Docker 集群中的 Node.js 应用程序： ```yaml global: scrape_...

prometheus使用docker_sd_config监控docker集群

2023-05-31 上传
要使用 `docker_sd_config` 监控 Docker 集群，需要在 Prometheus 的配置文件中设置相应的服务发现规则。以下是一个示例配置文件，用于监控运行在 Docker 集群中的 Node.js 应用程序： ```yaml global: scrape_...

0 * * * * /var/lib/docker/containers/clean_docker_log.sh

2024-07-18 上传
`/var/lib/docker/containers/clean_docker_log.sh` 是要执行的具体命令，即清理Docker容器的日志文件。 `clean_docker_log.sh` 应该是一个脚本文件，它位于/var/lib/docker/containers目录下，这个目录通常保存着...
qq_30512059
  • 粉丝: 2
  • 资源: 59
上传资源 快速赚钱

最新资源