cannot access /dls/ops-data

[ronaldomercado]

The container does not load those folders.

This is only slightly inconvenient.

[MJGaughran]

Is it appropriate to load this folder by default for everyone? How do permissions work in this area?

You can add in additional mounts in your launch script. Perhaps we should include a command-line argument to provide additional mounts in the run-dev-c7.sh script?

It is worthwhile asking whether we want to completely replicate a RHEL7 workstation, or just provide the necessary functionality with some sensible restrictions?

[gilesknap]

I like the idea of adding extra mounts on the command line options.

The permissions for any mounts should work as normal I believe since all SELinux and secondary groups are handled.

There is also no significant cost to adding mounts that I'm aware of (maybe slower startup for the first invocation) so we could add this one.

[MJGaughran]

I don't know what the permissions are like in the /dls/ops-data folder, but if I'm able to affect it at all I wouldn't want it included.

I would prefer being able to opt-in to or opt-out of these things. Even though dev-c7 is for general purpose use, I appreciate using it as a sandbox.

Obviously, we already have that problem elsewhere. I would personally vote for the ability to exclude things like read-write access to filesystems (excluding e.g. current directory) through command-line options, but I'm not going to be upset if other people disagree.

[gilesknap]

@MJGaughran I don't have a problem with making the file system mounts configurable.

Do you mean you want Read only access to the full list or no access? Note that quite a bit of dls_sw is needed for many of our tools to work, but read only would be OK for most tools.

[MJGaughran]

I don't have an issue with read-only access.

[gilesknap]

I think we need to make the mounts configurable see #57