我对Docker中的整个数据量过程有疑问.基本上这里有两个Dockerfiles及其各自的运行命令:
Dockerfile 1 -
# Transmission over Debian
#
# Version 2.92
FROM debian:testing
RUN apt-get update \
&& apt-get -y install nano \
&& apt-get -y install transmission-daemon transmission-common transmission-cli \
&& mkdir -p /transmission/config /transmission/watch /transmission/download
ENTRYPOINT ["transmission-daemon", "--foreground"]
CMD ["--config-dir", "/transmission/config", "--watch-dir", "/transmission/watch", "--download-dir", "/transmission/download", "--allowed", "*", "--no-blocklist", "--no-auth", "--no-dht", "--no-lpd", "--encryption-preferred"]
Run Code Online (Sandbox Code Playgroud)
命令1 -
docker run --name transmission -d -p 9091:9091 -v C:\path\to\config:/transmission/config -v C:\path\to\watch:/transmission/watch -v C:\path\to\download:/transmission/download transmission
Run Code Online (Sandbox Code Playgroud)
Dockerfile 2 -
# Nginx over Debian
#
# …
Run Code Online (Sandbox Code Playgroud) 我正在尝试创建一个新的 Kubernetes 部署,该部署允许我在重新启动或关闭时保留 Pod 的状态。仅供参考,Kubernetes 实例是一个托管的 Amazon EKS 集群,我正在尝试合并一个安装到 Pod 的由 Amazon EFS 支持的持久卷。
不幸的是,正如我现在所拥有的,PV 按需要安装/etc/
,但内容几乎是空的,除了一些在启动过程中修改的文件。
部署 yaml 如下所示:
kind: Deployment
apiVersion: apps/v1
spec:
replicas: 1
selector:
matchLabels:
app: testpod
template:
metadata:
creationTimestamp: null
labels:
app: testpod
spec:
volumes:
- name: efs
persistentVolumeClaim:
claimName: efs
containers:
- name: testpod
image: 'xxxxxxxxxxxx.dkr.ecr.us-east-2.amazonaws.com/testpod:latest'
args:
- /bin/init
ports:
- containerPort: 443
protocol: TCP
resources: {}
volumeMounts:
- name: efs
mountPath: /etc
subPath: etc
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
imagePullPolicy: IfNotPresent
securityContext:
capabilities: …
Run Code Online (Sandbox Code Playgroud) docker kubernetes persistent-volumes persistent-volume-claims amazon-eks