Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mention that sudo -u postgres throws an error #458

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ElvisDot
Copy link
Contributor

@ElvisDot ElvisDot commented Mar 5, 2024

Running sudo -u postgres psql --command "CREATE ROLE \"`whoami`\" LOGIN createdb superuser;" in the users home folder within ubuntu WSL throws the following error

could not change directory to "/home/student_name": Permission denied

The student doing the setup is expeceted to be in his /home/username folder. Which on WSL ubuntu by default is not accessible to other users on the system. So when the su command switches user, the postgres user can not access the current directory and that is throwing the permission error.

Which is fine because it does not have to access the current folder at all. It just has to connect to the postgres database which usually works. So the permission warning is followed by the success output CREATE ROLE.

This might not be obvious to someone following the setup for the first time. To reduce useless debugging there is now a note hidden in a spoiler that says that this error is okay.

Running ```sudo -u postgres psql --command "CREATE ROLE \"`whoami`\" LOGIN createdb superuser;"```
in the users home folder within ubuntu WSL throws the following error

```
could not change directory to "/home/student_name": Permission denied
```

The student doing the setup is expeceted to be in his /home/username folder.
Which on WSL ubuntu by default is not accessible to other users on the system.
So when the `su` command switches user, the postgres user can not access
the current directory and that is throwing the permission error.

Which is fine because it does not have to access the current folder at all.
It just has to connect to the postgres database which usually works.
So the permission warning is followed by the success output `CREATE ROLE`.

This might not be obvious to someone following the setup for the first time.
To reduce useless debugging there is now a note hidden in a spoiler that
says that this error is okay.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant