Developing KDE PIM with Docker

[David Jarvie]

On Thursday 02 Nov 2017 11:05:18 Sandro Knauß wrote:
> Hey,
> 
> > That's what I did. Both folders I tried existed before I ran docker, and
> > they were owned by the user (not root), with the usual permissions.
> 
> I use also the docker script and do not face this problem at all.
> outside the docker:
> % ls -lsa ~/kdepim-dev
> total 136
>  4 drwxr-xr-x  9 me me  4096 Okt 30 11:18 ./
> 68 drwxr-xr-x 99 me me 65536 Nov  2 11:03 ../
> 
> cmd:
> ~/git/kdepim-docker/run.sh ~/kdepim-dev
> 
> inside docker it looks for me like this:
> neon at baedc5b0dfed:~$ ls -lsa ~/kdepim
> total 76
> 4 drwxr-xr-x  9 neon admin 4096 Oct 30 10:18 .
> 8 drwxr-xr-x  1 neon neon  4096 Nov  2 10:00 ..

Running the 'ls' commands gives the same permissions and ownerships for me. 
However, when I try to create any file in ~/kdepim in the docker instance, I 
always get an error message "Read-only file system".

The docker command which run.sh executes is

sudo docker run -ti -e DISPLAY -e ICECC_SERVER -v=/tmp/.X11-unix:/tmp/.X11-
unix:rw,z -v=/run/user/1000/pulse:/run/user/1000/pulse:rw,z -
v=/home/david/kdepim-dev:/home/neon/kdepim:rw,z --privileged --name kdepim-dev 
kdepim:dev

So ~/kdepim-dev *should* be mounted read-write, but for some reason must be 
getting mounted read-only. There is no error message when I start docker.

-- 
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm