Can't seem to docker-compose up after last update
Closed this issue · 3 comments
AlexKalopsia commented
Just pulled the latest image, and when doing docker-compose up
I get this
postgres_1 |
postgres_1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres_1 |
postgres_1 | 2020-06-02 18:55:40.661 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
postgres_1 | 2020-06-02 18:55:40.661 UTC [1] LOG: listening on IPv6 address "::", port 5432
redis_1 | 1:C 02 Jun 2020 18:55:40.211 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 02 Jun 2020 18:55:40.211 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 02 Jun 2020 18:55:40.211 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1 | 1:M 02 Jun 2020 18:55:40.213 * Running mode=standalone, port=6379.
redis_1 | 1:M 02 Jun 2020 18:55:40.213 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1 | 1:M 02 Jun 2020 18:55:40.213 # Server initialized
redis_1 | 1:M 02 Jun 2020 18:55:40.213 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1 | 1:M 02 Jun 2020 18:55:40.213 * Ready to accept connections
postgres_1 | 2020-06-02 18:55:40.664 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1 | 2020-06-02 18:55:40.707 UTC [25] LOG: database system was shut down at 2020-06-02 18:51:06 UTC
postgres_1 | 2020-06-02 18:55:40.731 UTC [1] LOG: database system is ready to accept connections
app_1 | bundler: command not found: bin/rails
app_1 | Install missing gem executables with `bundle install`
wreeto_app_1 exited with code 127
If I do docker-compose up -d
it does go up but i cannot reach wreeto
chrisvel commented
@AlexKalopsia Can you please docker-compose down
and then up
again? Also can you provide your .env
file (mask If something is sensitive)?
I just installed docker and pulled the latest image - everything seems ok. I need to reproduce the issue.
chrisvel commented
@AlexKalopsia did you have the chance to solve this issue ?
chrisvel commented
I am closing this issue due to inactivity.