Named volume against `/data` results in permissions error about ignition-docker HOT 2 CLOSED

Hey -- it seems like any of your mapped aliases result in a permissions error. Going through the docker it just seems like the ignition user doesn't have permissions for those paths.

I haven't had time to go through the dockerfile, but I think the solution would just be to do a

sudo chown -R $USER ~/.folderPath

as part of the build process. Moving this weekend, gonna try to create a pull request when I have time. If you get there first I wouldn't be mad about it.

from ignition-docker.

Currently /data doesn't exist within the build, and in the entrypoint its existence is what triggers seeding that location with the original files from /var/lib/ignition/data and then relinking everything. I could include /data in the image and assign the appropriate permissions (like I do for everything else), then use a more explicit detection of a mount (like what I do for the double-mount detection here) to define DATA_VOLUME_LOCATION. This would ensure that the base permissions are set appropriately...

from ignition-docker.