You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What version of this package are you using?
MASTER What operating system, Node.js, and npm version?
Docker compose - ubuntu What happened?
ran docker-compose run --rm web bash -lc 'bin/rails db:create db:migrate' as part of the instructions
receive the following error
Errno::EACCES: Permission denied @ rb_sysopen - /home/app/wedding/db/schema.rb
Creating wedding_web_run ... done
Rails Error: Unable to access log file. Please ensure that /home/app/wedding/log/development.log exists and is writable (ie, make it writable for user and group: chmod 0664 /home/app/wedding/log/development.log). The log level has been raised to WARN and the output directed to STDERR until the problem is fixed.
dug a bit deeper, seems the dockerfile is running nodejs 10 and ruby is behind...not sure if related but either way. cant build.
What did you expect to happen?
Are you willing to submit a pull request to fix this bug?
The text was updated successfully, but these errors were encountered:
What version of this package are you using?
MASTER
What operating system, Node.js, and npm version?
Docker compose - ubuntu
What happened?
ran docker-compose run --rm web bash -lc 'bin/rails db:create db:migrate' as part of the instructions
receive the following error
Errno::EACCES: Permission denied @ rb_sysopen - /home/app/wedding/db/schema.rb
Creating wedding_web_run ... done
Rails Error: Unable to access log file. Please ensure that /home/app/wedding/log/development.log exists and is writable (ie, make it writable for user and group: chmod 0664 /home/app/wedding/log/development.log). The log level has been raised to WARN and the output directed to STDERR until the problem is fixed.
dug a bit deeper, seems the dockerfile is running nodejs 10 and ruby is behind...not sure if related but either way. cant build.
What did you expect to happen?
Are you willing to submit a pull request to fix this bug?
The text was updated successfully, but these errors were encountered: