v5.8 启动失败(openEuler，docker)请帮忙看下

h_cq · 2024 年10 月 23 日 08:45

版本：emqx/emqx:5.8.1
系统：Linux version 6.6.0-28.0.0.34.oe2403.x86_64 (root@dc-64g.compass-ci) (gcc_old (GCC) 12.3.1 (openEuler 12.3.1-30.oe2403), GNU ld (GNU Binutils) 2.41) #1 SMP Mon May 27 22:22:46 CST 2024

报错信息standard_init_linux.go:228: exec user process caused: permission denied

docker-compost

version: '3.8'
services:
  emqx:
    image: emqx/emqx:5.8.1
    ports:
      - "1883:1883"
      - "8081:8081"
      - "8083:8083"
      - "8084:8084"
      - "8883:8883"
      - "18083:18083"

尝试过把 data log 都挂载出来并设置为 777
尝试过把添加 emqx 用户并加入 wheel

zhongwencool · 2024 年10 月 23 日 09:49

没有遇到过，这看起来有点像是docker本身的问题，
可以尝试先用 docker 运行一个最简单的image

docker run hello-world

如果也有问题，再加上 sudo

sudo docker run hello-world

如果还不行，我是在 3 个类似的问题下找到的，你看看照着他们说的能解决不。

github.com/mattermost/mattermost-docker

Getting "standard_init_linux.go:207: exec user process caused "permission denied"" inside docker container for mattermost_app

opened 04:27PM - 09 Jul 19 UTC

Philippe-Cote-Morneault

Hi, I followed every instruction from the readme and everything seemed to work f…ine. I'll show you the exact commands I made in case someone sees something odd. **Step 1)** My `docker-compose.yml` ``` version: "2" services: db: build: db read_only: true restart: unless-stopped volumes: - /srv/docker/db/var/lib/postgresql/data:/var/lib/postgresql/data - /etc/localtime:/etc/localtime:ro environment: - POSTGRES_USER=mmuser - POSTGRES_PASSWORD=mmuser_password - POSTGRES_DB=mattermost # uncomment the following to enable backup # - AWS_ACCESS_KEY_ID=XXXX # - AWS_SECRET_ACCESS_KEY=XXXX # - WALE_S3_PREFIX=s3://BUCKET_NAME/PATH # - AWS_REGION=us-east-1 app: build: context: app # uncomment following lines for team edition or change UID/GID args: - edition=team # - PUID=1000 # - PGID=1000 restart: unless-stopped volumes: - /srv/docker/mattermost/config:/mattermost/config:rw - /srv/docker/mattermost/data:/mattermost/data:rw - /srv/docker/mattermost/logs:/mattermost/logs:rw - /srv/docker/mattermost/plugins:/mattermost/plugins:rw - /srv/docker/mattermost/client-plugins:/mattermost/client/plugins:rw - /etc/localtime:/etc/localtime:ro environment: # set same as db credentials and dbname - MM_USERNAME=mmuser - MM_PASSWORD=mmuser_password - MM_DBNAME=mattermost # in case your config is not in default location #- MM_CONFIG=srv/docker/mattermost/config/config.json ``` **Step 2)** `docker-compose build` ``` [root@Services mattermost]# sudo docker-compose build Building db Step 1/9 : FROM postgres:9.4-alpine ---> 2ae8b40b46ba Step 2/9 : ENV DEFAULT_TIMEZONE UTC ---> Using cache ---> 809432053715 Step 3/9 : RUN apk add --no-cache build-base curl libc6-compat libffi-dev linux-headers python-dev py-pip py-cryptography && pip --no-cache-dir install 'wal-e<1.0.0' envdir && rm -rf /var/cache/apk/* /tmp/* /var/tmp/* ---> Using cache ---> 09dfa519d897 Step 4/9 : COPY setup-wale.sh /docker-entrypoint-initdb.d/ ---> Using cache ---> cda3a31b6167 Step 5/9 : HEALTHCHECK CMD pg_isready -U $POSTGRES_USER -d $POSTGRES_DB || exit 1 ---> Using cache ---> fc400a70dab4 Step 6/9 : COPY entrypoint.sh / ---> Using cache ---> 6d07469eb0f3 Step 7/9 : ENTRYPOINT ["/entrypoint.sh"] ---> Using cache ---> 0159df721fdc Step 8/9 : CMD ["postgres"] ---> Using cache ---> a1b721c2631f Step 9/9 : VOLUME ["/var/run/postgresql", "/usr/share/postgresql/", "/var/lib/postgresql/data", "/tmp", "/etc/wal-e.d/env"] ---> Using cache ---> 294684934a74 Successfully built 294684934a74 Successfully tagged mattermost_db:latest Building app Step 1/17 : FROM alpine:3.9 ---> 055936d39205 Step 2/17 : ENV PATH="/mattermost/bin:${PATH}" ---> Using cache ---> 9d6a0fffdb84 Step 3/17 : ENV MM_VERSION=5.12.1 ---> Using cache ---> b6dc01a9e98a Step 4/17 : ARG edition=enterprise ---> Using cache ---> 6dae4885d74f Step 5/17 : ARG PUID=2000 ---> Using cache ---> 718dda2298ff Step 6/17 : ARG PGID=2000 ---> Using cache ---> 805ed0b45d0f Step 7/17 : ARG MM_BINARY= ---> Using cache ---> c0620b13375e Step 8/17 : RUN apk add --no-cache ca-certificates curl jq libc6-compat libffi-dev linux-headers mailcap netcat-openbsd xmlsec-dev tzdata && rm -rf /tmp/* ---> Using cache ---> 3353b0e9a425 Step 9/17 : RUN mkdir -p /mattermost/data /mattermost/plugins /mattermost/client/plugins && if [ ! -z "$MM_BINARY" ]; then curl $MM_BINARY | tar -xvz ; elif [ "$edition" = "team" ] ; then curl https://releases.mattermost.com/$MM_VERSION/mattermost-team-$MM_VERSION-linux-amd64.tar.gz | tar -xvz ; else curl https://releases.mattermost.com/$MM_VERSION/mattermost-$MM_VERSION-linux-amd64.tar.gz | tar -xvz ; fi && cp /mattermost/config/config.json /config.json.save && rm -rf /mattermost/config/config.json && addgroup -g ${PGID} mattermost && adduser -D -u ${PUID} -G mattermost -h /mattermost -D mattermost && chown -R mattermost:mattermost /mattermost /config.json.save /mattermost/plugins /mattermost/client/plugins ---> Using cache ---> bc1e025d5b83 Step 10/17 : USER mattermost ---> Using cache ---> 900623daede4 Step 11/17 : HEALTHCHECK CMD curl --fail http://localhost:8000 || exit 1 ---> Using cache ---> da6a00a99ac8 Step 12/17 : COPY entrypoint.sh / ---> Using cache ---> 734204ff7588 Step 13/17 : ENTRYPOINT ["/entrypoint.sh"] ---> Using cache ---> a109c66adddd Step 14/17 : WORKDIR /mattermost ---> Using cache ---> 5592fa2cd167 Step 15/17 : CMD ["mattermost"] ---> Using cache ---> 094b696a4be5 Step 16/17 : EXPOSE 8000 ---> Using cache ---> aabdc40197c3 Step 17/17 : VOLUME ["/mattermost/data", "/mattermost/logs", "/mattermost/config", "/mattermost/plugins", "/mattermost/client/plugins"] ---> Using cache ---> 5e0df1de442c Successfully built 5e0df1de442c Successfully tagged mattermost_app:latest ``` **Step 3)** Create volumes `[root@organisationServices mattermost]# mkdir -p /srv/docker/mattermost/{data,logs,config,plugins}` **Step 4)** Give permissions to volumes `[root@organisationServices mattermost]# sudo chown -R 2000:2000 /srv/docker/mattermost/` **Step 5)** `docker-compose up` ``` [root@organisationServices mattermost]# sudo docker-compose up -d Starting mattermost_db_1 ... done Starting mattermost_app_1 ... done ``` Everything seems fine up to here. Also, I am root user, so the permission steps was optional but I did it anyways. Here's what happens when I log the `mattermost_app_1` container: ``` [root@organisationServices mattermost]# docker container logs mattermost_app_1 standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" standard_init_linux.go:207: exec user process caused "permission denied" ``` I can't find a way to get more logging information about this container. Also, this is the status for both containers: ``` [root@organisationServices mattermost]# docker container ls CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 119f95d8275a mattermost_app "/entrypoint.sh matt…" 39 hours ago Restarting (1) 17 seconds ago mattermost_app_1 b3a1b116cf12 mattermost_db "/entrypoint.sh post…" 39 hours ago Up About a minute (healthy) 5432/tcp ``` So the container keeps restarting with the same error logs. Does anyone have any idea how to fix this and what is the issue? Also, I am new to Docker. I want to host my database in my own `postgres` database without creating one with Mattermost. My only issue is understanding what would be the host for said database when adding it in `docker-compose`. What is the host of a database inside a docker container so I can add it in the `docker-compose`? Thanks!

github.com/docker-library/hello-world

standard_init_linux.go:175: exec user process caused "permission denied"

opened 03:32AM - 05 Aug 16 UTC

closed 08:08PM - 30 May 18 UTC

liuxiaopiao

question

I can run other images successfully but when running the hello-world, it fails: … [root@vm ~]# docker run hello-world standard_init_linux.go:175: exec user process caused "permission denied" **And my docker info is like below:** [root@vm ~]# docker info Containers: 9 Running: 1 Paused: 0 Stopped: 8 Images: 3 Server Version: 1.12.0-rc5 Storage Driver: btrfs Build Version: Btrfs v3.17 Library Version: 101 Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: host bridge null overlay Swarm: inactive Runtimes: runc Default Runtime: runc Security Options: seccomp selinux Kernel Version: 4.1.12-37.6.1.el7uek.x86_64 Operating System: Oracle Linux Server 7.0 OSType: linux Architecture: x86_64 CPUs: 2 Total Memory: 7.135 GiB Name: slc00bpv.us.oracle.com ID: QY4D:Q26Y:RHTS:QNUR:NEKC:LSBB:LPR7:ECKG:DRID:EQPJ:3MHG:Z5K6 Docker Root Dir: /scratch/docker Debug Mode (client): false Debug Mode (server): false Http Proxy: http://www-proxy.us.oracle.com:80 Https Proxy: http://www-proxy.us.oracle.com:80 No Proxy: localhost,127.0.0.0/8,.us.oracle.com,.oraclecorp.com,/var/run/docker.sock Registry: https://index.docker.io/v1/ WARNING: bridge-nf-call-ip6tables is disabled Insecure Registries: dte.docker.oraclecorp.com 127.0.0.0/8 **And my vm info is** [root@vm ~]# uname -a Linux vm 4.1.12-37.6.1.el7uek.x86_64 #2 SMP Thu Jul 28 10:59:49 PDT 2016 x86_64 x86_64 x86_64 GNU/Linux Could you please help me on this?

github.com/grafana/grafana

Failed to start docker container: exec user process caused "permission denied"

opened 03:49PM - 13 Jan 19 UTC

closed 05:19PM - 23 Jan 19 UTC

leikao

needs more info

### What Grafana version are you using? Latest version, the mater branch. ##…# What OS are you running grafana on? Fedora ### What did you do? Git clone grafana's latest code from github, then `sudo make build-docker-dev` to build a docker image. When running the docker image I got the following error: > $ docker run -it -p 3000:3000 grafana/grafana:dev > standard_init_linux.go:207: exec user process caused "permission denied" File permision details: > $ docker run -it --user root --entrypoint sh grafana/grafana:dev > # ls -l /run.sh > -rwxr-x---. 1 root root 3350 Jan 13 14:57 /run.sh