Unable to start container due to directory permissions

Alongside my pulp development repos I have a directory of various RPM repos - despite not being referenced in the configuration at all, I get the following error when I try to start the environment:

Error: unable to start container aedae1b7800720aeb9bc1053adbb782a422875db8ea2a767078d395c30bc6fb0: lsetxattr /home/dalley/devel/repos: operation not permitted

I'm guessing it wants to recursively make everything under ~/devel available inside the container but doesn't like the permissions on that one directory?

It appears a while back I made it owned by the nginx user to make it easy to symlink to /usr/share/nginx/html/ or something.

-rw-r--r--.  1 dalley dalley    2419 Apr 21 21:48 repo_list.txt
drwxrwxrwx. 15 nginx  nginx   151552 Aug 24 23:53 repos
-rw-r--r--.  1 dalley dalley    4885 Apr 21 14:42 repo_sizes.txt

You can see it has permissions 777 so any user can read it.

After using chown and chgrp on this directory with my own user it all works so this isn't a critical issue, just nice to address if possible.

Start by reproducing the environment startup with a directory owned by another user, using the reported lsetxattr error as the initial clue. Investigate how directory permissions and extended attributes are handled during container startup; done means the environment starts successfully without requiring ownership changes, or the limitation is clearly documented.