Rails Docker docker-compose db:create db:migrate 出来ない

Question

Docker docker-compose db:create db:migrate 出来ない

既存アプリケーションの開発環境にdockerを適用させようと思ったのですが、

docker-compose build

の後に、

docker-compose run web rails db:create db:migrate
や
docker-compose run web bundle exec rails db:create db:migrate

といったコマンドを叩いても、

Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "exec: \"rails\": executable file not found in $PATH": unknown

と表示されてしまいます。

docker-compose up

上記コマンドは通り、ページを表示しようとしてくれています(migrateされていないので表示自体はできませんが)

色々な記事を参考にしてみたのですが、
どれもうまくいかず途方に暮れている状態です、、、。
もし、これが原因かもしれないなどあれば、ご教示いただけますと幸いです。

開発環境

ruby2.5.5
rails 5.2.4.1
docker 19.03.1
windows 10 home

現状

source 'https://rubygems.org'
git_source(:github) { |repo| "https://github.com/#{repo}.git" }

ruby '2.5.5'

# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
gem 'rails', '~> 5.2.4'
# Use sqlite3 as the database for Active Record
gem 'sqlite3'
# Use postgresql as the database for Active Record
gem 'pg', '~> 0.18'
# Use Puma as the app server
gem 'puma', '~> 3.11'
# Use SCSS for stylesheets
gem 'sass-rails', '~> 5.0'
# Use Uglifier as compressor for JavaScript assets
gem 'uglifier', '>= 1.3.0'
# See https://github.com/rails/execjs#readme for more supported runtimes
# gem 'mini_racer', platforms: :ruby

# Use CoffeeScript for .coffee assets and views
gem 'coffee-rails', '~> 4.2'
# Turbolinks makes navigating your web application faster. Read more: https://github.com/turbolinks/turbolinks
# gem 'turbolinks', '~> 5'
# Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder
gem 'jbuilder', '~> 2.5'
# Use Redis adapter to run Action Cable in production
# gem 'redis', '~> 4.0'
# Use ActiveModel has_secure_password
# gem 'bcrypt', '~> 3.1.7'

# Use ActiveStorage variant
# gem 'mini_magick', '~> 4.8'

# Use Capistrano for deployment
# gem 'capistrano-rails', group: :development

# Reduces boot times through caching; required in config/boot.rb
gem 'bootsnap', '>= 1.1.0', require: false

group :development, :test do
  # Call 'byebug' anywhere in the code to stop execution and get a debugger console
  gem 'byebug', platforms: [:mri, :mingw, :x64_mingw]
  gem 'pry-rails'
  gem 'pry-byebug'
  gem 'pry-doc'
  gem 'better_errors','2.5.1'
  gem 'binding_of_caller','0.8.0'
  gem 'rspec-rails','3.9.0'
  gem 'factory_bot_rails','~> 5.1.1'
end

group :development do
  # Access an interactive console on exception pages or by calling 'console' anywhere in the code.
  gem 'web-console', '>= 3.3.0'
  gem 'listen', '>= 3.0.5', '< 3.2'
  # Spring speeds up development by keeping your application running in the background. Read more: https://github.com/rails/spring
  gem 'spring'
  gem 'spring-watcher-listen', '~> 2.0.0'
end

FROM ruby:2.5.5

RUN apt-get update && apt-get install -y nodejs --no-install-recommends && rm -rf /var/lib/apt/lists/*
RUN apt-get update && apt-get install -y postgresql-client --no-install-recommends && rm -rf /var/lib/apt/lists/*
RUN apt-get update -qq && apt-get install -y build-essential libpq-dev nodejs

WORKDIR /myapp

ADD Gemfile /myapp/Gemfile
ADD Gemfile.lock /myapp/Gemfile.lock

RUN gem install bundler
RUN bundle install

ADD . /myapp

CMD ["bundle", "exec", "rails", "server", "-b", "0.0.0.0"]

#!/bin/bash
set -e

# Remove a potentially pre-existing server.pid for Rails.
rm -f /myapp/tmp/pids/server.pid

# Then exec the container's main process (what's set as CMD in the Dockerfile).
exec "$@"

version: '3'
services:
  db:
    image: postgres
    volumes:
      - ./tmp/db:/var/lib/postgresql/data
  web:
    build:
      context: .
      dockerfile: Dockerfile
    command: bash -c "rm -f tmp/pids/server.pid && bundle exec rails s -p 3000 -b '0.0.0.0'"
    volumes:
      - .:/myapp
    ports:
      - "3000:3000"
    depends_on:
      - db

default: &default
  adapter: postgresql
  encoding: unicode
  host: db
  username: postgres
  password:
  pool: 5

development:
  <<: *default
  database: myapp_development


test:
  <<: *default
  database: myapp_test

他、必要情報などあれば伝えさせていただければと思います。
無駄な情報も多いかもしれませんが、何卒ご容赦頂ければ幸いです。
よろしくお願いいたします。

Answer 1

下記を削除することで、dbが起動しdb:create等が可能となりました。
ただこれでは永続化が出来ない状況のため色々方法を探したいと思います。

    volumes:
      - ./tmp/db:/var/lib/postgresql/data

Answer 2

dbとwebのコンテナが分かれているので、dbをバックグラウンドで起動したままrun webをする必要があります。

Comments

[UMAweb1]

ご回答誠にありがとうございます。
返信遅れてしまい申し訳ございません。
仰る通り、dbが起動されていないようなのですが、コマンドを叩いてみたり、再度アプリの作り直しから行っても、以下のエラーが発生する状況です、、。
db_1 | ****************************************************
db_1 | WARNING: No password has been set for the database.
db_1 | This will allow anyone with access to the
db_1 | Postgres port to access your database. In
db_1 | Docker's default configuration, this is
db_1 | effectively any other container on the same
db_1 | system.
db_1 |
db_1 | Use "-e POSTGRES_PASSWORD=password" to set
db_1 | it in "docker run".
db_1 | ****************************************************
db_1 | The files belonging to this database system will be owned by user "postgres".
db_1 | This user must also own the server process.
db_1 |
db_1 | The database cluster will be initialized with locale "en_US.utf8".
db_1 | The default database encoding has accordingly been set to "UTF8".
db_1 | The default text search configuration will be set to "english".
db_1 |
db_1 | Data page checksums are disabled.
db_1 |
db_1 | fixing permissions on existing directory /var/lib/postgresql/data ... ok
db_1 | creating subdirectories ... ok
db_1 | selecting dynamic shared memory implementation ... posix
db_1 | selecting default max_connections ... 20
db_1 | selecting default shared_buffers ... 400kB
db_1 | selecting default time zone ... Etc/UTC
db_1 | creating configuration files ... ok
db_1 | running bootstrap script ... 2020-01-04 03:14:38.022 UTC [80] FATAL: data directory "/var/lib/postgresql/data" has wrong ownership
db_1 | 2020-01-04 03:14:38.022 UTC [80] HINT: The server must be started by the user that owns the data directory.
db_1 | child process exited with exit code 1
db_1 | initdb: removing contents of data directory "/var/lib/postgresql/data"