Hello! I would like to publish mongodb as a classically confined snap. The snap needs to be able to read and write to the host filesystem at a user-defined path. Many of the db components in various charms need to be able to all write to the same directory that is defined by the user, and the system-files interface does not allow for a dynamically configured path.
Is this an acceptable reason to publish this snap classically?
I’m actually not convinced that this should be a classic snap, to be honest. I think we should be striving for strict snaps for our databases. There will be some edge cases around storage, but I suspect with existing interfaces such as removable-media, system-files, system-backup and others, we’ll be able to get to a working solution.
What if I expose /data/db using the system files interface and require the use of a symlink at /data/db to point to another directory? This would allow a user to define a directory path. Is that technically possible or does the confinement interfere with that?
@jardon are you still wanting classic confinement for this snap? If so you need to provide some justification as to why this is required, and to which of the supported categories listed at Process for reviewing classic confinement snaps you believe the mongodb snap fits within. As from what I can see it doesn’t really appear to fit within any of the existing categories, and I can’t see any great justification as to why this snap is not able to work under strict confinement.