kubernetes mysql chown operation not permitted

I am currently experimenting with Kubernetes and have installed a small cluster on ESX infra I had running here locally. I installed two slave nodes with a master node using Project Atomic with Fedora. The cluster is all installed fine and seems to be running. However I first want to get a MySQL container up and running, but no matter what I try i cannot get it to run.

apiVersion: v1
kind: Pod
metadata:
  name: mysql
  labels: 
    name: mysql
spec: 
  containers: 
    - resources:
       limits :
          cpu: 0.5
      image: mysql:5.6
      name: mysql
      env:
        - name: MYSQL_ROOT_PASSWORD
          value: myPassw0rd
      ports: 
        - containerPort: 3306
          name: mysql
      volumeMounts:
        - name: mysql-persistent-storage
          mountPath: /var/lib/mysql
  volumes:
    - name: mysql-persistent-storage
      nfs:
        server: 10.0.0.2
        path: "/export/mysql"

For the volume I already tried all kinds of solutions, I tried using persistent volume with and without claim. I tried using host volume and emptyDir, but I always end up with this error when the container starts:

  • Docker Busybox container add groups and user
  • Spring Cloud Config Server cannot connect to git over ssh in Docker
  • Marathon command run docker-compose up error
  • how to write a dockerfile to run a sbt project in container
  • SaltStack doesn't start docker container
  • How to install docker-compose on Linux RHEL 6.6?
  • chown: changing ownership of ‘/var/lib/mysql/’: Operation not permitted

    I must be doing something stupid, but no idea what to do here?

  • repair command in mongodb in docker container
  • Installing maven in a docker build overrides JAVA 8 with JAVA 7(!)
  • Docker run vs create
  • Container doesn't exist after Rest API successfully creates it
  • Dockerrun.aws.json file for private dockerhub image
  • Monitoring Glassfish 4 on Docker with JVisualVM
  • One Solution collect form web for “kubernetes mysql chown operation not permitted”

    Ok it seems I can answer my own question, the problem was lying in the NFS share that was being used as the persistent volume. I had it set to ‘squash_all’ in the export but it needs to have a ‘no_root_squash’ to allow root in case of docker container to chown on the nfs bound volume.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.