This issue is more serious than you think. For instance, I want to create /tmp as ephemeral. Normally, I assign 1777 permissions to /tmp to allow users to create and delete own files/directories from /tmp. That's very common for very large set of programs. If I set up tmp in cloud- init definition as
- [ ephemeral0, /tmp, auto, 'defaults,nobootwait,noatime', '0', '2' ] it means that permission will be 0755 every time after reboot. It makes cloud-init unusable and requires extra hacks such as creating upstart script to fix the permission on /tmp during boot process as stated at http://serverfault.com/questions/427626/how-to-mount-tmp-in-mnt-on-ec2 As a solution you should either implement as mounts: ephemeral0: - [/tmp, auto, 'defaults,nobootwait,noatime', '0', '2' ] - [/tmp, "root:root, 1777] or [ ephemeral0, /tmp, 'defaults', '0', '2', 'ubuntu:ubuntu', '0755'] otherwise this bug makes cloud-init not very usable for mount management -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/893786 Title: mount option can`t set permissions To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/893786/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
