Great that your attempting to get it working in docker. I remember reading an email or two about this... Is this related to the way that docker containers use that copy on write filesystem or maybe the AUFS that docker uses as default for setup of container?
> On Apr 14, 2014, at 9:11 PM, Luis Pabon <[email protected]> wrote: > > Hi guys, > I am investigating running smoke tests inside Docker.io, but I cannot seem > to pass the posix-compliance tests. I then tried to run the posix-compliance > tests on XFS and EXT4 but I could make them pass there either. This is what > I did: > > $ truncate -s 5G mydisk > $ sudo mkfs.xfs mydisk > $ sudo mount -o loop mydisk /mnt > $ cd /mnt > * Change the value of 'fs' in ~/qa/tools/posix-compliance/conf according to > the file system format. > $ prove -r ~/qa/tools/posix-compliance/tests > > They always fail on chown tests. Anyone know why? > > - Luis > > _______________________________________________ > Gluster-devel mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/gluster-devel _______________________________________________ Gluster-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/gluster-devel
