Project

General

Profile

Actions

Bug #29932

closed

docker-compose error on step 10/47

Added by Manuel Saks almost 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Development tools
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

After run "docker-compose up" I have an error:

Step 10/47 : COPY extras/containers/entrypoint.sh /usr/bin/
ERROR: Service 'worker' failed to build: COPY failed: stat /var/lib/docker/tmp/docker-builder771789171/extras/containers/entrypoint.sh: no such file or directory

I didn't change anything in "docker-compose.yml" except host names etc.

OS: Debian 10

I was trying to handle it by myself editing Dockerfile, but without success.

Actions #1

Updated by Manuel Saks almost 4 years ago

  • Category deleted (foreman-installer script)
Actions #2

Updated by Manuel Saks almost 4 years ago

I tried just create the entrypoint.sh file inside of Dockerfile with:

RUN echo "#!/bin/bash" \
"set -e" \
"export PATH=~/bin:${GEM_HOME}/bin:${PATH}" \
"rm -f ~/pids/server.pid" \
"exec "$
"" > /var/lib/docker/tmp/docker-builder771789171/extras/containers/entrypoint.sh@

using the file that I found on the server:

"/var/lib/docker/overlay2/6ca835493bbf80cd43e3d65bf15b9768533fb7b22b9c026a8050588fcd66874d/diff/usr/src/app/extras/containers/entrypoint.sh"

without result.

Actions #3

Updated by Manuel Saks almost 4 years ago

  • Priority changed from Normal to High
Actions #4

Updated by Ewoud Kohl van Wijngaarden almost 4 years ago

  • Project changed from Installer to Foreman
  • Category set to Development tools
  • Priority changed from High to Normal
  • Difficulty deleted (easy)

The installer doesn't do anything with Docker. Foreman does have a docker-compose config

Actions #5

Updated by Manuel Saks almost 4 years ago

Yup, I was trying with the docker-compose from github.
https://github.com/theforeman/foreman/blob/develop/docker-compose.yml

Actions #6

Updated by Ohad Levy almost 4 years ago

can you confirm it works with the images published at quay.io instead of building it yourself?

Actions #7

Updated by Manuel Saks almost 4 years ago

Also can't run it.

Details:

user@host:/docker$ sudo docker run quay.io/foreman/foreman
2020-05-26T18:25:35 [I|app|] Rails cache backend: File
=> Booting Puma
=> Rails 6.0.2.2 application starting in production
=> Run `rails server --help` for more startup options
Exiting
bundler: failed to load command: bin/rails (bin/rails)
RuntimeError: Cannot load database configuration:
Could not load database configuration. No such file - ["config/database.yml"]
/home/foreman/vendor/ruby/2.6.0/gems/railties-6.0.2.2/lib/rails/application/configuration.rb:241:in `database_configuration'
/home/foreman/vendor/ruby/2.6.0/gems/activerecord-6.0.2.2/lib/active_record/railtie.rb:200:in `block (2 levels) in <class:Railtie>'
/home/foreman/vendor/ruby/2.6.0/gems/activesupport-6.0.2.2/lib/active_support/lazy_load_hooks.rb:72:in `class_eval'
/home/foreman/vendor/ruby/2.6.0/gems/activesupport-6.0.2.2/lib/active_support/lazy_load_hooks.rb:72:in `block in execute_hook'
/home/foreman/vendor/ruby/2.6.0/gems/activesupport-6.0.2.2/lib/active_support/lazy_load_hooks.rb:62:in `with_execution_control'
/home/foreman/vendor/ruby/2.6.0/gems/activesupport-6.0.2.2/lib/active_support/lazy_load_hooks.rb:67:in `execute_hook'
/home/foreman/vendor/ruby/2.6.0/gems/activesupport-6.0.2.2/lib/active_support/lazy_load_hooks.rb:43:in `block in on_load'
/home/foreman/vendor/ruby/2.6.0/gems/activesupport-6.0.2.2/lib/active_support/lazy_load_hooks.rb:42:in `each'
/home/foreman/vendor/ruby/2.6.0/gems/activesupport-6.0.2.2/lib/active_support/lazy_load_hooks.rb:42:in `on_load'
/home/foreman/vendor/ruby/2.6.0/gems/activerecord-6.0.2.2/lib/active_record/railtie.rb:198:in `block in <class:Railtie>'
/home/foreman/vendor/ruby/2.6.0/gems/railties-6.0.2.2/lib/rails/initializable.rb:32:in `instance_exec'
/home/foreman/vendor/ruby/2.6.0/gems/railties-6.0.2.2/lib/rails/initializable.rb:32:in `run'
/home/foreman/vendor/ruby/2.6.0/gems/railties-6.0.2.2/lib/rails/initializable.rb:61:in `block in run_initializers'
/usr/share/ruby/tsort.rb:228:in `block in tsort_each'
/usr/share/ruby/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
/usr/share/ruby/tsort.rb:431:in `each_strongly_connected_component_from'
/usr/share/ruby/tsort.rb:349:in `block in each_strongly_connected_component'
/usr/share/ruby/tsort.rb:347:in `each'
/usr/share/ruby/tsort.rb:347:in `call'
/usr/share/ruby/tsort.rb:347:in `each_strongly_connected_component'
/usr/share/ruby/tsort.rb:226:in `tsort_each'
/usr/share/ruby/tsort.rb:205:in `tsort_each'
/home/foreman/vendor/ruby/2.6.0/gems/railties-6.0.2.2/lib/rails/initializable.rb:60:in `run_initializers'
/home/foreman/vendor/ruby/2.6.0/gems/railties-6.0.2.2/lib/rails/application.rb:363:in `initialize!'
/home/foreman/vendor/ruby/2.6.0/gems/railties-6.0.2.2/lib/rails/railtie.rb:190:in `public_send'
/home/foreman/vendor/ruby/2.6.0/gems/railties-6.0.2.2/lib/rails/railtie.rb:190:in `method_missing'
/home/foreman/config/environment.rb:5:in `<top (required)>'
/home/foreman/vendor/ruby/2.6.0/gems/activesupport-6.0.2.2/lib/active_support/dependencies.rb:325:in `require'
/home/foreman/vendor/ruby/2.6.0/gems/activesupport-6.0.2.2/lib/active_support/dependencies.rb:325:in `block in require'
/home/foreman/vendor/ruby/2.6.0/gems/activesupport-6.0.2.2/lib/active_support/dependencies.rb:291:in `load_dependency'
/home/foreman/vendor/ruby/2.6.0/gems/activesupport-6.0.2.2/lib/active_support/dependencies.rb:325:in `require'
config.ru:5:in `block in <main>'
/home/foreman/vendor/ruby/2.6.0/gems/rack-2.0.9/lib/rack/builder.rb:55:in `instance_eval'
/home/foreman/vendor/ruby/2.6.0/gems/rack-2.0.9/lib/rack/builder.rb:55:in `initialize'
config.ru:in `new'
config.ru:in `<main>'
/home/foreman/vendor/ruby/2.6.0/gems/rack-2.0.9/lib/rack/builder.rb:49:in `eval'
/home/foreman/vendor/ruby/2.6.0/gems/rack-2.0.9/lib/rack/builder.rb:49:in `new_from_string'
/home/foreman/vendor/ruby/2.6.0/gems/rack-2.0.9/lib/rack/builder.rb:40:in `parse_file'
/home/foreman/vendor/ruby/2.6.0/gems/rack-2.0.9/lib/rack/server.rb:319:in `build_app_and_options_from_config'
/home/foreman/vendor/ruby/2.6.0/gems/rack-2.0.9/lib/rack/server.rb:219:in `app'
/home/foreman/vendor/ruby/2.6.0/gems/rack-2.0.9/lib/rack/server.rb:354:in `wrapped_app'
/home/foreman/vendor/ruby/2.6.0/gems/rack-2.0.9/lib/rack/server.rb:283:in `start'
/home/foreman/vendor/ruby/2.6.0/gems/railties-6.0.2.2/lib/rails/commands/server/server_command.rb:39:in `start'
/home/foreman/vendor/ruby/2.6.0/gems/railties-6.0.2.2/lib/rails/commands/server/server_command.rb:147:in `block in perform'
/home/foreman/vendor/ruby/2.6.0/gems/railties-6.0.2.2/lib/rails/commands/server/server_command.rb:138:in `tap'
/home/foreman/vendor/ruby/2.6.0/gems/railties-6.0.2.2/lib/rails/commands/server/server_command.rb:138:in `perform'
/home/foreman/vendor/ruby/2.6.0/gems/thor-1.0.1/lib/thor/command.rb:27:in `run'
/home/foreman/vendor/ruby/2.6.0/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command'
/home/foreman/vendor/ruby/2.6.0/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch'
/home/foreman/vendor/ruby/2.6.0/gems/railties-6.0.2.2/lib/rails/command/base.rb:69:in `perform'
/home/foreman/vendor/ruby/2.6.0/gems/railties-6.0.2.2/lib/rails/command.rb:46:in `invoke'
/home/foreman/vendor/ruby/2.6.0/gems/railties-6.0.2.2/lib/rails/commands.rb:18:in `<top (required)>'
/home/foreman/vendor/ruby/2.6.0/gems/activesupport-6.0.2.2/lib/active_support/dependencies.rb:325:in `require'
/home/foreman/vendor/ruby/2.6.0/gems/activesupport-6.0.2.2/lib/active_support/dependencies.rb:325:in `block in require'
/home/foreman/vendor/ruby/2.6.0/gems/activesupport-6.0.2.2/lib/active_support/dependencies.rb:291:in `load_dependency'
/home/foreman/vendor/ruby/2.6.0/gems/activesupport-6.0.2.2/lib/active_support/dependencies.rb:325:in `require'
bin/rails:9:in `<top (required)>'

Actions #8

Updated by Ohad Levy almost 4 years ago

I'm a bit confused, a couple of items:

- you are not suppose to run it as a single container, you need additional services such as db, redis etc, its meant to either running using docker-compose or kubernetes (I maintain a version that I use at https://github.com/ohadlevy/foreman-kube/)
- you are rebuilding the published images, did you try to do docker-compose pull or are you building it with a different plugin combinations (see https://github.com/theforeman/foreman/blob/develop/developer_docs/containers.asciidoc for more usage details).

Actions #9

Updated by Manuel Saks almost 4 years ago

  • Status changed from New to Resolved

I was using docker-compose on multiple containers.
It worked after I pulled the image.
Thanks for your patience. :)

Actions

Also available in: Atom PDF