Issue with file ownership (user 1000)

[JeanLucEsser]

Hi there,

I do have some strange issue with the latest beta (10).

Ownership of my project files in the vm is ubuntu:ubuntu (ubuntu is user 1000) which seems ok.
Ownership of my project files in my local folder is my-user:staff for some files, and 1000:1000 for many others, as if it wanted them to be the user ubuntu which doesn't exists locally on my machine.

If I edit a file in the vm, it changes the ownership locally to 1000:1000 each and every time.

Attached is a local and remote ls of a default craft install.

[jasonmccallister]

@JeanLucEsser which version of nitro are you using?

[JeanLucEsser]

I'm using nitro beta 10 which is the latest I believe.

[jasonmccallister]

@JeanLucEsser lets try the following, can you perform the following steps?

1. Stop the machine using nitro stop
2. Change directories to the one above the affected sites: cd <dir/above/uc-senat-project>
3. Force the user and group on the files using sudo chown -R <username>:<group> <uc-senate>
4. Run nitro start
5. Edit the files in the vm using nitro ssh
6. Verify the files permissions have not changed

Hopefully that will resolve the issue.

[JeanLucEsser]

@jasonmccallister yes it did resolve the issue.

I did the exact same thing previously without first stopping nitro and it didn't work.
I'll keep you posted if the permissions change again.

Have you been able to reproduce the issue on a fresh install?

1. Start machine
2. Create project directory on local
3. Run nitro add from project directory
4. SSH into machine
5. Composer install Craft to project directory
6. Verify permissions in local project directory

[jasonmccallister]

I was able to reproduce it in an earlier beta when running nitro refresh. I can't reproduce it from a new machine on beta-10 that I created yesterday.

[jasonmccallister]

@JeanLucEsser is this still an issue for you?

[JeanLucEsser]

Unfortunately it is. I didn't follow suit because it looks like you cannot reproduce it from a new machine so maybe it is something with my setup, I'll try to find some time to fully start from scratch to see how it goes.

Something I can tell you is that forcing the user and group on the files almost did the trick. I still get the package.* files reverting to the wrong permission every time I make an npm install from the machine. For the record npm has been installed on the new machine via n-install (curl -L https://git.io/n-install | bash).

What do you think we should do in the meantime? It looks I'm the only one with this issue.

[jasonmccallister]

We just released Nitro 2 where we switched from Multipass to Docker and added a ton of new features. Please see the announcement for more details.

This issue was specific to Multipass so we are going to close this out. Please see the documentation on upgrading from Nitro 1.