GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Embed Notice

HTML Code

Corresponding Notice

  1. Embed this notice
    Julio J. 🀲 (j3j5@hachyderm.io)'s status on Wednesday, 07-Dec-2022 12:31:49 JSTJulio J. 🀲Julio J. 🀲
    in reply to

    OK, just for the record, I've found *a solution*. I don't like it and it does feel hacky, although otoh it doesn't feel too wrong.

    Add an extra initContainer with busybox and chown the shared volume with the desired uid and gid. It's ugly but it works. If nobody throws a big reason why I shouldn't be doing this, I'm going to leave it like this.

    Thanks for the boosts #hachyderm !

    Source https://discuss.kubernetes.io/t/write-permissions-on-volume-mount-with-security-context-fsgroup-option/16524

    In conversationWednesday, 07-Dec-2022 12:31:49 JST from hachyderm.iopermalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: global.discourse-cdn.com
      Write permissions on volume mount with security context fsgroup option
      I’m trying to run a tomcat container in K8S with a non-root user, to do so I set User ‘tomcat’ with the appropriate permission in Docker Image. I have a startup script that creates a directory in /opt/var/logs (during container startup) and also starts tomcat service. #steps in Dockerfile #adding tomcat user and group and permission to /opt directory addgroup tomcat -g 1001 && \ adduser -D -u 1001 -G tomcat tomcat && \ chown -R tomcat:tomcat /opt #switch user User tomcat The pod runs fine in ...
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.