環(huán)境：Kubernetes version: v1.16.3 OS: CentOS 7 Kernel: Linux k8s02-master01 3.10.0-1062.4.3.el7.x86_64發(fā)生了什么：我有一個(gè)運(yùn)行從自定義 Apache/Wordpress 圖像構(gòu)建的容器的 Wordpress 部署。我嘗試使用 Wordpress 管理員上傳插件，但插件文件夾默認(rèn)為 777 權(quán)限。僅插件文件夾，而不是它們的文件。注意到/var/www/html默認(rèn)情況下設(shè)置為 777，然后我嘗試chmod 755 /var/www/html在容器上下文中手動(dòng)...它有效，新插件文件夾默認(rèn)為 755，但它不是持久的。嘗試在 Dockerfile 中進(jìn)行 chmod，但它不起作用，/var/www/html仍然默認(rèn)為 777。當(dāng)我使用官方 Wordpress 圖像而不是我的 Dockerfile 時(shí)，同樣的問題。是否可以默認(rèn)/var/www/html為 755 權(quán)限？DOCKERFILE (wordpress-test:5.2.4-apache):FROM wordpress:5.2.4-apacheRUN sed -i 's/Listen 80/Listen 8080/g' /etc/apache2/ports.conf;RUN sed -i 's/:80/:8080/g' /etc/apache2/sites-enabled/000-default.conf;RUN sed -i 's/#ServerName www.example.com/ServerName localhost/g' /etc/apache2/sites-enabled/000-default.conf;RUN /bin/bash -c 'ls -la /var/www; chmod 755 /var/www/html; ls -la /var/www'EXPOSE 8080CMD ["apache2-foreground"]DockerFILE 構(gòu)建日志：Step 8/10 : RUN /bin/bash -c 'ls -la /var/www; chmod 755 /var/www/html; ls -la /var/www'; ---> Running in 7051d46dd9f3total 12drwxr-xr-x 1 root root 4096 Oct 17 14:22 .drwxr-xr-x 1 root root 4096 Oct 17 14:22 ..drwxrwxrwx 2 www-data www-data 4096 Oct 17 14:28 htmltotal 12drwxr-xr-x 1 root root 4096 Oct 17 14:22 .drwxr-xr-x 1 root root 4096 Oct 17 14:22 ..drwxr-xr-x 2 www-data www-data 4096 Oct 17 14:28 html在容器上下文中檢查結(jié)果：$ kubectl exec -it <POD_NAME> -n development -- sh(inside the container) $ ls -la /var/wwwtotal 12drwxr-xr-x. 1 root root 4096 Oct 17 14:22 .drwxr-xr-x 1 root root 4096 Oct 17 14:22 ..drwxrwxrwx 5 www-data www-data 4096 Dec 17 05:40 html/var/www/html仍然默認(rèn)為 777。
1 回答
慕桂英3389331
TA貢獻(xiàn)2036條經(jīng)驗(yàn) 獲得超8個(gè)贊
在kubernetes 中，您可以借助initContainers更改已掛載卷的權(quán)限。您的部署可能如下所示：
apiVersion: apps/v1
kind: Deployment
metadata:
name: blog-wordpress
namespace: development
labels:
app: blog
spec:
selector:
matchLabels:
app: blog
tier: wordpress
replicas: 4
strategy:
type: RollingUpdate
rollingUpdate:
maxSurge: 2
maxUnavailable: 2
template:
metadata:
labels:
app: blog
tier: wordpress
spec:
volumes:
- name: blog-wordpress
persistentVolumeClaim:
claimName: blog-wordpress
initContainers:
- name: permission-fix
image: busybox
command: ["/bin/chmod","-R","755", "/var/www/html"]
volumeMounts:
- name: blog-wordpress
mountPath: /var/www/html/wp-content
containers:
- name: blog-wordpress
# image: wordpress:5.2.4-apache
image: wordpress-test:5.2.4-apache
securityContext:
runAsUser: 33
runAsGroup: 33
allowPrivilegeEscalation: false
capabilities:
add:
- "NET_ADMIN"
- "NET_BIND_SERVICE"
- "SYS_TIME"
resources:
requests:
cpu: "250m"
memory: "64Mi"
limits:
cpu: "500m"
memory: "128Mi"
ports:
- name: liveness-port
containerPort: 8080
readinessProbe:
initialDelaySeconds: 15
httpGet:
path: /index.php
port: 8080
timeoutSeconds: 15
periodSeconds: 15
failureThreshold: 5
livenessProbe:
initialDelaySeconds: 10
httpGet:
path: /index.php
port: 8080
timeoutSeconds: 10
periodSeconds: 15
failureThreshold: 5
env:
# Database
- name: WORDPRESS_DB_HOST
value: blog-mysql
- name: WORDPRESS_DB_NAME
value: wordpress
- name: WORDPRESS_DB_USER
valueFrom:
secretKeyRef:
name: blog-mysql
key: username
- name: WORDPRESS_DB_PASSWORD
valueFrom:
secretKeyRef:
name: blog-mysql
key: password
- name: WORDPRESS_TABLE_PREFIX
value: wp_
- name: WORDPRESS_AUTH_KEY
valueFrom:
secretKeyRef:
name: blog-wordpress
key: auth-key
- name: WORDPRESS_SECURE_AUTH_KEY
valueFrom:
secretKeyRef:
name: blog-wordpress
key: secure-auth-key
- name: WORDPRESS_LOGGED_IN_KEY
valueFrom:
secretKeyRef:
name: blog-wordpress
key: logged-in-key
- name: WORDPRESS_NONCE_KEY
valueFrom:
secretKeyRef:
name: blog-wordpress
key: nonce-key
- name: WORDPRESS_AUTH_SALT
valueFrom:
secretKeyRef:
name: blog-wordpress
key: auth-salt
- name: WORDPRESS_SECURE_AUTH_SALT
valueFrom:
secretKeyRef:
name: blog-wordpress
key: secure-auth-salt
- name: WORDPRESS_LOGGED_IN_SALT
valueFrom:
secretKeyRef:
name: blog-wordpress
key: logged-in-salt
- name: WORDPRESS_NONCE_SALT
valueFrom:
secretKeyRef:
name: blog-wordpress
key: nonce-salt
- name: WORDPRESS_CONFIG_EXTRA
value: |
define('WPLANG', 'fr_FR');
define('WP_CACHE', false);
define('WP_MEMORY_LIMIT', '64M');
volumeMounts:
- name: blog-wordpress
mountPath: "/var/www/html/wp-content"
編輯： 但是請(qǐng)記住，您只能更改已安裝文件夾的權(quán)限，而不是父文件夾/文件夾。因此，在上面的示例中，您可以使用：
command: ["/bin/chmod","-R","755", "/var/www/html"]
但它只會(huì)更改/var/www/html/wp-content目錄的權(quán)限。如果您可以準(zhǔn)備好您的卷，使其包含/var/www/html目錄并且可以這樣安裝，您將能夠設(shè)置其權(quán)限。
讓我知道它是否有幫助。
- 1 回答
- 0 關(guān)注
- 202 瀏覽
添加回答
舉報(bào)
0/150
提交
取消