Does not start within docker
g-wolter opened this issue · 1 comments
The app does not start with docker.
Steps to reproduce:
- Clone repository into /opt/
- Start with
make run
- Builds image
On startup the process exits with
ERROR: Encountered errors while bringing up the project.
make: *** [Makefile:2: run] Fehler 1```
During the build process there are some warnings
Step 8/12 : RUN GEM=$(gem build taskwarrior-web.gemspec | awk '/File: .*/{ print
---> Running in 57124a669b44
WARNING: open-ended dependency on sinatra (>= 0) is not recommended
if sinatra is semantically versioned, use:
add_runtime_dependency 'sinatra', '> 0'> 0'
WARNING: open-ended dependency on parseconfig (>= 0) is not recommended
if parseconfig is semantically versioned, use:
add_runtime_dependency 'parseconfig', '
WARNING: open-ended dependency on vegas (>= 0) is not recommended
if vegas is semantically versioned, use:
add_runtime_dependency 'vegas', '> 0'> 0'
WARNING: open-ended dependency on rinku (>= 0) is not recommended
if rinku is semantically versioned, use:
add_runtime_dependency 'rinku', '
WARNING: open-ended dependency on versionomy (>= 0) is not recommended
if versionomy is semantically versioned, use:
add_runtime_dependency 'versionomy', '> 0'> 0'
WARNING: open-ended dependency on sinatra-simple-navigation (>= 0) is not recommended
if sinatra-simple-navigation is semantically versioned, use:
add_runtime_dependency 'sinatra-simple-navigation', '
WARNING: open-ended dependency on rack-flash3 (>= 0) is not recommended
if rack-flash3 is semantically versioned, use:
add_runtime_dependency 'rack-flash3', '> 0'> 0'
WARNING: open-ended dependency on rack-test (>= 0, development) is not recommended
if rack-test is semantically versioned, use:
add_development_dependency 'rack-test', '
WARNING: open-ended dependency on rspec-html-matchers (>= 0, development) is not recommended
if rspec-html-matchers is semantically versioned, use:
add_development_dependency 'rspec-html-matchers', '~> 0'
WARNING: See http://guides.rubygems.org/specification-reference/ for help
OS: 5.5.4-arch1-1
Docker: Docker version 19.03.6-ce, build 369ce74a3c
Docker-compose: docker-compose version 1.25.3, build d4d1b42b
Task: 2.5.1
The configuration of task has not been altered.
Cannot really help you with your specific problem, just my 2 cents: I just started it via docker on my machine (xubuntu 19.10). I see those warnings, but it still works as expected.
Versions of docker & docker-compose (quite old version, I know) I used:
$ docker-compose version
docker-compose version 1.18.0, build 8dd22a9
docker-py version: 2.6.1
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.1t 3 May 2016
$ docker version
Client: Docker Engine - Community
Version: 19.03.3
API version: 1.40
Go version: go1.12.10
Git commit: a872fc2f86
Built: Tue Oct 8 01:00:44 2019
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.3
API version: 1.40 (minimum version 1.12)
Go version: go1.12.10
Git commit: a872fc2f86
Built: Tue Oct 8 00:59:17 2019
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.2.10
GitCommit: b34a5c8af56e510852c35414db4c1f4fa6172339
runc:
Version: 1.0.0-rc8+dev
GitCommit: 3e425f80a8c931f88e6d94a8c831b9d5aa481657
docker-init:
Version: 0.18.0
GitCommit: fec3683