Upgrade to 3.0 docker failed

Graylog Central (peer support)
1

docker logs are such as:
chown /usr/share/graylog/***** permission denied…

2

again what is your question? How should someone help you with this two lines?

3

below is the docker-compose.yml

version: '2'
services:
  # MongoDB: https://hub.docker.com/_/mongo/
  mongodb:
    image: mongo:3
    restart: unless-stopped
    volumes:
      - mongo_data:/data/graylog/mongodb/data
  # Elasticsearch: https://www.elastic.co/guide/en/elasticsearch/reference/6.x/docker.html
  elasticsearch:
    image: docker.elastic.co/elasticsearch/elasticsearch-oss:6.5.4
    volumes:
      - es_data:/data/graylog/elasticsearch/data
    environment:
      - http.host=0.0.0.0
      - transport.host=localhost
      - network.host=0.0.0.0
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
    ulimits:
      memlock:
        soft: -1
        hard: -1
    mem_limit: 1g
    restart: unless-stopped
  # Graylog: https://hub.docker.com/r/graylog/graylog/
  graylog:
    image: graylog/graylog:3.0
    volumes:
      - graylog_journal:/data/graylog/data/journal
    environment:
      # CHANGE ME!
      - GRAYLOG_PASSWORD_SECRET=ymuBu87F9E8sHnYL
      # Password: admin
      - GRAYLOG_ROOT_PASSWORD_SHA2=b295d9fce9a18fbd2c6f74752b47c0988cdb07fa8acf035301913e040f7b192c
      - GRAYLOG_ROOT_EMAIL=zhangcheng@cloud-scale.cn
      - GRAYLOG_ROOT_TIMEZONE=Asia/Shanghai
      - GRAYLOG_HTTP_BIND_ADDRESS=127.0.0.1:9000
      - GRAYLOG_HTTP_EXTERNAL_URI=http://cloudscale.iok.la:9000/
      - GRAYLOG_TRANSPORT_EMAIL_ENABLED=true
      - GRAYLOG_TRANSPORT_EMAIL_HOSTNAME=smtp.mxhichina.com
      - GRAYLOG_TRANSPORT_EMAIL_PORT=25
      - GRAYLOG_TRANSPORT_EMAIL_USE_TLS=false
      - GRAYLOG_TRANSPORT_EMAIL_USE_SSL=false
      - GRAYLOG_TRANSPORT_EMAIL_USE_AUTH=true
      - GRAYLOG_TRANSPORT_EMAIL_AUTH_USERNAME=zhangcheng@cloud-scale.cn
      - GRAYLOG_TRANSPORT_EMAIL_AUTH_PASSWORD=JPOKUyehZcSqb9PTrAckNKfQ0UWIZ9fa
      - GRAYLOG_TRANSPORT_EMAIL_SUBJECT_PREFIX=[graylog]
      - GRAYLOG_TRANSPORT_EMAIL_FROM_EMAIL=zhangcheng@cloud-scale.cn
    restart: unless-stopped
    links:
      - mongodb:mongo
      - elasticsearch
    depends_on:
      - mongodb
      - elasticsearch
    ports:
      # Graylog web interface and REST API
      - 9000:9000
      # Syslog TCP
      - 514:514
      # Syslog UDP
      - 5154:514/udp
      # GELF TCP
      - 12201:12201
      # GELF UDP
      - 12201:12201/udp
volumes:
  mongo_data:
    driver: local
  es_data:
    driver: local
  graylog_journal:
    driver: local

matrix@cs-code ~/C/graylog> docker logs graylog_graylog_1
chown: changing ownership of '/usr/share/graylog/data/journal/recovery-point-offset-checkpoint': Operation not permitted
chown: changing ownership of '/usr/share/graylog/data/journal/messagejournal-0/00000000000002678684.index': Operation not permitted
chown: changing ownership of '/usr/share/graylog/data/journal/messagejournal-0/00000000000002678684.log': Operation not permitted
chown: changing ownership of '/usr/share/graylog/data/journal/recovery-point-offset-checkpoint': Operation not permitted
chown: changing ownership of '/usr/share/graylog/data/journal/messagejournal-0/00000000000002678684.index': Operation not permitted
chown: changing ownership of '/usr/share/graylog/data/journal/messagejournal-0/00000000000002678684.log': Operation not permitted
chown: changing ownership of '/usr/share/graylog/data/journal/recovery-point-offset-checkpoint': Operation not permitted
chown: changing ownership of '/usr/share/graylog/data/journal/messagejournal-0/00000000000002678684.index': Operation not permitted
chown: changing ownership of '/usr/share/graylog/data/journal/messagejournal-0/00000000000002678684.log': Operation not permitted
4

what did you not understand on the error message?

Anyway - I have merged this PR into the Images ( https://github.com/Graylog2/graylog-docker/pull/67 ) and I’m going to build new images today. That will include the fix.

5

i don’t know how to fix…

6

change the ownership of the attached volumen from inside the container once and it should work.

Graylog has run before as root and now runs as Graylog - that is why this need to be fixed once.

7

thanks for your help

8

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.