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
Followed the instructions in the README, then added some labels in the compose for accessing web and other endpoints and tried start it all up. Camo and Web are unhealthy:
➜ feedbin git:(feedbin) ✗ sudo docker-compose ps
Name Command State Ports
--------------------------------------------------------------------------------------------
feedbin-camo npm start Up (unhealthy) 8081/tcp
feedbin-elasticsearch /docker-entrypoint.sh elas ... Up (healthy) 9200/tcp, 9300/tcp
feedbin-extract node app/server.js Up
feedbin-image bundle exec foreman start Up
feedbin-memcached docker-entrypoint.sh memcached Up 11211/tcp
feedbin-minio /usr/bin/docker-entrypoint ... Up (healthy) 9000/tcp
feedbin-minio-create mc Exit 1
feedbin-postgres docker-entrypoint.sh postgres Up (healthy) 5432/tcp
feedbin-redis docker-entrypoint.sh redis ... Up (healthy) 6379/tcp
feedbin-refresher bundle exec foreman start Up
feedbin-web bundle exec rails s --port ... Up (unhealthy) 3000/tcp
feedbin-workers foreman start Up 3000/tcp
➜ feedbin git:(feedbin) ✗ sudo docker-compose logs feedbin-camo
Attaching to feedbin-camo
feedbin-camo | npm info it worked if it ends with ok
feedbin-camo | npm info using npm@5.3.0
feedbin-camo | npm info using node@v8.4.0
feedbin-camo | npm info lifecycle camo@2.3.0~prestart: camo@2.3.0
feedbin-camo | npm info lifecycle camo@2.3.0~start: camo@2.3.0
feedbin-camo |
feedbin-camo | > camo@2.3.0 start /opt/camo
feedbin-camo | > node server.js
feedbin-camo |
feedbin-camo | SSL-Proxy running on 8081 with node:v8.4.0 pid:16 version:2.3.0.
feedbin-camo | npm info lifecycle camo@2.3.0~poststart: camo@2.3.0
feedbin-camo |
feedbin-camo | ┌──────────────────────────────────────────────────────────┐
feedbin-camo | │ npm update check failed │
feedbin-camo | │ Try running with sudo or get access │
feedbin-camo | │ to the local update config store via │
feedbin-camo | │ sudo chown -R $USER:$(id -gn $USER) /nonexistent/.config │
feedbin-camo | └──────────────────────────────────────────────────────────┘
feedbin-camo | npm info ok
feedbin-camo | npm info it worked if it ends with ok
feedbin-camo | npm info using npm@5.3.0
feedbin-camo | npm info using node@v8.4.0
feedbin-camo | npm info lifecycle camo@2.3.0~prestart: camo@2.3.0
feedbin-camo | npm info lifecycle camo@2.3.0~start: camo@2.3.0
feedbin-camo |
feedbin-camo | > camo@2.3.0 start /opt/camo
feedbin-camo | > node server.js
feedbin-camo |
feedbin-camo | SSL-Proxy running on 8081 with node:v8.4.0 pid:16 version:2.3.0.
feedbin-camo | npm info lifecycle camo@2.3.0~poststart: camo@2.3.0
feedbin-camo |
feedbin-camo | ┌──────────────────────────────────────────────────────────┐
feedbin-camo | │ npm update check failed │
feedbin-camo | │ Try running with sudo or get access │
feedbin-camo | │ to the local update config store via │
feedbin-camo | │ sudo chown -R $USER:$(id -gn $USER) /nonexistent/.config │
feedbin-camo | └──────────────────────────────────────────────────────────┘
feedbin-camo | npm info ok
feedbin-camo | npm info it worked if it ends with ok
feedbin-camo | npm info using npm@5.3.0
feedbin-camo | npm info using node@v8.4.0
feedbin-camo | npm info lifecycle camo@2.3.0~prestart: camo@2.3.0
feedbin-camo | npm info lifecycle camo@2.3.0~start: camo@2.3.0
feedbin-camo |
feedbin-camo | > camo@2.3.0 start /opt/camo
feedbin-camo | > node server.js
feedbin-camo |
feedbin-camo | SSL-Proxy running on 8081 with node:v8.4.0 pid:17 version:2.3.0.
feedbin-camo | npm info lifecycle camo@2.3.0~poststart: camo@2.3.0
feedbin-camo |
feedbin-camo | ┌──────────────────────────────────────────────────────────┐
feedbin-camo | │ npm update check failed │
feedbin-camo | │ Try running with sudo or get access │
feedbin-camo | │ to the local update config store via │
feedbin-camo | │ sudo chown -R $USER:$(id -gn $USER) /nonexistent/.config │
feedbin-camo | └──────────────────────────────────────────────────────────┘
feedbin-camo | npm info ok
feedbin-camo | npm info it worked if it ends with ok
feedbin-camo | npm info using npm@5.3.0
feedbin-camo | npm info using node@v8.4.0
feedbin-camo | npm info lifecycle camo@2.3.0~prestart: camo@2.3.0
feedbin-camo | npm info lifecycle camo@2.3.0~start: camo@2.3.0
feedbin-camo |
feedbin-camo | > camo@2.3.0 start /opt/camo
feedbin-camo | > node server.js
feedbin-camo |
feedbin-camo | SSL-Proxy running on 8081 with node:v8.4.0 pid:17 version:2.3.0.
feedbin-camo | npm info lifecycle camo@2.3.0~poststart: camo@2.3.0
feedbin-camo |
feedbin-camo | ┌──────────────────────────────────────────────────────────┐
feedbin-camo | │ npm update check failed │
feedbin-camo | │ Try running with sudo or get access │
feedbin-camo | │ to the local update config store via │
feedbin-camo | │ sudo chown -R $USER:$(id -gn $USER) /nonexistent/.config │
feedbin-camo | └──────────────────────────────────────────────────────────┘
feedbin-camo | npm info ok
feedbin-camo | npm info it worked if it ends with ok
feedbin-camo | npm info using npm@5.3.0
feedbin-camo | npm info using node@v8.4.0
feedbin-camo | npm info lifecycle camo@2.3.0~prestart: camo@2.3.0
feedbin-camo | npm info lifecycle camo@2.3.0~start: camo@2.3.0
feedbin-camo |
feedbin-camo | > camo@2.3.0 start /opt/camo
feedbin-camo | > node server.js
feedbin-camo |
feedbin-camo | SSL-Proxy running on 8081 with node:v8.4.0 pid:16 version:2.3.0.
➜ feedbin git:(feedbin) ✗ sudo docker-compose logs feedbin-web
Attaching to feedbin-web
feedbin-web | => Booting Puma
feedbin-web | => Rails 6.1.4 application starting in production
feedbin-web | => Run `bin/rails server --help` for more startup options
feedbin-web | I, [2021-07-14T16:26:34.100744 #1] INFO -- honeybadger: ** [Honeybadger] Initializing Honeybadger Error Tracker for Ruby. Ship it! version=4.8.0 framework=rails level=1 pid=1
feedbin-web | Puma starting in single mode...
feedbin-web | * Puma version: 5.3.2 (ruby 2.7.3-p183) ("Sweetnighter")
feedbin-web | * Min threads: 5
feedbin-web | * Max threads: 5
feedbin-web | * Environment: production
feedbin-web | * PID: 1
feedbin-web | * Listening on http://0.0.0.0:3000
feedbin-web | Use Ctrl-C to stop
feedbin-web | - Gracefully stopping, waiting for requests to finish
feedbin-web | Exiting
feedbin-web | => Booting Puma
feedbin-web | => Rails 6.1.4 application starting in production
feedbin-web | => Run `bin/rails server --help` for more startup options
feedbin-web | I, [2021-07-14T16:30:19.312310 #1] INFO -- honeybadger: ** [Honeybadger] Initializing Honeybadger Error Tracker for Ruby. Ship it! version=4.8.0 framework=rails level=1 pid=1
feedbin-web | Puma starting in single mode...
feedbin-web | * Puma version: 5.3.2 (ruby 2.7.3-p183) ("Sweetnighter")
feedbin-web | * Min threads: 5
feedbin-web | * Max threads: 5
feedbin-web | * Environment: production
feedbin-web | * PID: 1
feedbin-web | * Listening on http://0.0.0.0:3000
feedbin-web | Use Ctrl-C to stop
feedbin-web | - Gracefully stopping, waiting for requests to finish
feedbin-web | Exiting
feedbin-web | => Booting Puma
feedbin-web | => Rails 6.1.4 application starting in production
feedbin-web | => Run `bin/rails server --help` for more startup options
feedbin-web | I, [2021-07-14T16:30:45.402806 #1] INFO -- honeybadger: ** [Honeybadger] Initializing Honeybadger Error Tracker for Ruby. Ship it! version=4.8.0 framework=rails level=1 pid=1
feedbin-web | Puma starting in single mode...
feedbin-web | * Puma version: 5.3.2 (ruby 2.7.3-p183) ("Sweetnighter")
feedbin-web | * Min threads: 5
feedbin-web | * Max threads: 5
feedbin-web | * Environment: production
feedbin-web | * PID: 1
feedbin-web | * Listening on http://0.0.0.0:3000
feedbin-web | Use Ctrl-C to stop
feedbin-web | - Gracefully stopping, waiting for requests to finish
feedbin-web | Exiting
feedbin-web | => Booting Puma
feedbin-web | => Rails 6.1.4 application starting in production
feedbin-web | => Run `bin/rails server --help` for more startup options
feedbin-web | I, [2021-07-14T16:36:42.476081 #1] INFO -- honeybadger: ** [Honeybadger] Initializing Honeybadger Error Tracker for Ruby. Ship it! version=4.8.0 framework=rails level=1 pid=1
feedbin-web | Puma starting in single mode...
feedbin-web | * Puma version: 5.3.2 (ruby 2.7.3-p183) ("Sweetnighter")
feedbin-web | * Min threads: 5
feedbin-web | * Max threads: 5
feedbin-web | * Environment: production
feedbin-web | * PID: 1
feedbin-web | * Listening on http://0.0.0.0:3000
feedbin-web | Use Ctrl-C to stop
feedbin-web | - Gracefully stopping, waiting for requests to finish
feedbin-web | Exiting
feedbin-web | => Booting Puma
feedbin-web | => Rails 6.1.4 application starting in production
feedbin-web | => Run `bin/rails server --help` for more startup options
feedbin-web | I, [2021-07-14T16:46:09.660104 #1] INFO -- honeybadger: ** [Honeybadger] Initializing Honeybadger Error Tracker for Ruby. Ship it! version=4.8.0 framework=rails level=1 pid=1
feedbin-web | Puma starting in single mode...
feedbin-web | * Puma version: 5.3.2 (ruby 2.7.3-p183) ("Sweetnighter")
feedbin-web | * Min threads: 5
feedbin-web | * Max threads: 5
feedbin-web | * Environment: production
feedbin-web | * PID: 1
feedbin-web | * Listening on http://0.0.0.0:3000
feedbin-web | Use Ctrl-C to stop
➜ feedbin git:(feedbin) ✗
As I don't have an SMTP server or a Twitter account, I left those sections of the .env empty initially but then tried filling them with dummy values with no change I could tell. Here's the .env:
I'm trying to debug as I want to have better health checks. If I find any solution I can create a PR :)
Also I want to create a PR to update images to Alpine 3.14 and change how we build feedbin-web image (today we build it twice).
Followed the instructions in the README, then added some labels in the compose for accessing web and other endpoints and tried start it all up. Camo and Web are unhealthy:
As I don't have an SMTP server or a Twitter account, I left those sections of the .env empty initially but then tried filling them with dummy values with no change I could tell. Here's the .env:
and finally my
docker-compose.yaml
:The text was updated successfully, but these errors were encountered: