passenger-docker | Docker base images for Ruby , Python , Node.js and Meteor | Continuous Deployment library
kandi X-RAY | passenger-docker Summary
kandi X-RAY | passenger-docker Summary
Docker base images for Ruby, Python, Node.js and Meteor web apps
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of passenger-docker
passenger-docker Key Features
passenger-docker Examples and Code Snippets
Community Discussions
Trending Discussions on passenger-docker
QUESTION
I'm running a ruby sinatra app inside passenger within a docker container using one of the passenger-docker images(phusion/passenger-ruby26). This app is a simple web app that makes calls to a database(it does not constantly talk with the database, statements are only called when a certain button is clicked). I can start the app up fine and click around in my web app for a short amount of time but it always errors out at around 60 seconds of uptime saying:
Could not spawn process for application /home/app/my_app: A timeout occurred while starting a preloader process.
Error ID: 3b9633ef
Error details saved to: /tmp/passenger-error-aFglsc.html
Mind you this happens even when I don't click anything. Within the html file it states:
The Phusion Passenger application server tried to start the web application, but this took too much time, so Passenger put a stop to that.
It suggests that the server may be low on resources but I've given it unlimited resources(4 core 2.2GHz, 16GB ram, & 4GB swap), here are the load averages(memory used was 3%)
Here is the 'Problem Location', shows that it errored out at the 'Load Application' subprocess.
Things I've tried:
- Running passenger from Nginx(same error)
- Removing all stdout logging functions in my ruby app
- Increasing passenger_start_timeout
- Making sure folder/file privileges are set correctly
- Starting passenger with a custom nginx-config-template that maxes out timeouts and resources
- Gave my docker container unlimited resources
Tried a few other miscellaneous things that I can't recall but those didn't prove effective either.
Does anyone have any idea what might be going on? I'll provide more info if needed.
Versions used:
- Passenger 6.0.3
- Ruby 2.6.3
- Sinatra 2.0.5
- Docker 18.09.0
Running on MacOS 10.14.6
...ANSWER
Answered 2019-Oct-22 at 20:23Resolved. Turned out to be that I was running my ruby app twice. Had two instances of the run myapp command in the main app.rb and the config.ru rackup config file. Should only have one instance of that in ruby project.
QUESTION
I'm attempting to get a next.js app running in a docker container based on phusion/passenger-docker.
I have what I think is a complete setup based on passenger-docker documentation but I'm getting a 404 page from nginx.
A docker log dump shows that passenger or nginx, is looking for index.html
ANSWER
Answered 2019-Oct-05 at 07:39There are several subtle problems in the OP question.
Most notably, Passenger seems to require that the app root path, defined by root in the nginx configuration above, has a top level folder named public. This folder must not contain an index.html file and probably should be empty. This is shown in examples, but not spelled out as a hard requirement in the docs.
Second major error is that Passenger bypasses the port specified in the app's server.js (3000 in this case) and replaces it with the port specified in the nginx configuration. So the docker run command changed from:
docker container run --name nhe_app -p 80:3000 nhe_app
to
docker container run --name nhe_app -p 80:80 nhe_app.
Otherwise, the best advice I can give is:
- Learn the Passenger basics through a local installation (without Docker). Get the Passenger demo app working.
- Get your app working in that local Passenger installation.
- Apply what you have learned to implementing your app in passenger-docker.
QUESTION
Our docker build using passenger enterprise has stopped building.
We have the following error:
GPG error: https://www.phusionpassenger.com/enterprise_apt xenial Release: The following signatures were invalid: NODATA 2
At this stage in the Dockerfile
ANSWER
Answered 2018-Apr-10 at 09:05Phusion Passenger team member here. For anyone still experiencing this problem: unfortunately some gpg keys were not properly imported when we migrated to a new server yesterday. The issue should be resolved now, but if you are still experiencing issues, try running apt clean && rm -rf /var/lib/apt/lists/* && apt update
This will clear the local apt cache and retry the apt update. We are very sorry for the inconvenience caused by this.
QUESTION
TL;DR = Cannot get Passenger/Nginx to call our application from Django. "passenger-status" does not show proper Application Group that is shown in our currently live non-Docker server.
Trying to convert a live and running Passenger+Nginx+Django system to a Docker image. We started with the base Phusion:passenger-docker image and now trying to get it running like our live system. We followed the guide [here] but when we run the container, Passenger and Nginx do not run our application. Passenger provides the following output:
...ANSWER
Answered 2017-Apr-25 at 18:48Hmmm... Try adding:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install passenger-docker
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
