-
Notifications
You must be signed in to change notification settings - Fork 71
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
Provisioning fails with "id: oracle: no such user" #9
Comments
Are you getting this when you install for the first time? I raised #8 because I saw this sporadically when starting up - I can't find a way to get the shared folders to mount earlier - the solution is to just connect as sys and 'ALTER DATABASE OPEN'. Alternatively you could comment out the oradata shared folder as it is optional. |
Yes when provisioning. I assumed it was because Vagrant mounts the shared folders prior to running the "install.sh" script (which in turn installs Oracle and creates the 'oracle' user). This happens very early on in the provisioning process ("vagrant up"). Commenting out the oradata share works around the issue. Unsure if this is related to #8 as the db is not installed when this occurs. |
I Had that issue too :) first time i just ran the provisioning manually (
and did that check on the part causing the issue in the vagrantfile
|
Still have problems with this vagrant box. What I did.
|
I don't know how this should fix missing file issue, but I give it a try. UPDATE: It does not work by comment out line 35. Same error message. |
I am more software developer than administrator and currently facing same problem. Unfortunately the order in Vagrant File seems it doesn't matter when configure synced folder after shell executions. I found on Stackoverflow a solution what seems to me a valid one, but not sure. In the case here I changed the Vagrantfile: Maybe a valid solution? EDIT: the folder are then owned by vagrant:vagrant. |
Vagrant is attempting to mount "/vagrant/oradata" as user oracle before the user is created. This causes the provisioning to fail.
The text was updated successfully, but these errors were encountered: