Strange Error when installing postgres gem 'pg' about passenger-docker HOT 5 CLOSED

FWIW, the approach I'm using is to have a separate postgres container for the database.

You can link the containers together, then expose the host and port environment variables to your app, and put these environment variables in your database.yml file.

My basic configuration looks like:

# /etc/nginx/main.d/app_name.conf
env POSTGRES_PORT_5432_TCP_ADDR;
env POSTGRES_PORT_5432_TCP_PORT;

# /home/app/app_name/config/database.yml (for a rails app)
development:
  adapter: postgresql
  encoding: unicode
  database: name_this_database
  username: postgres
  password:
  host: <%= ENV['POSTGRES_PORT_5432_TCP_ADDR'] %>
  port: <%= ENV['POSTGRES_PORT_5432_TCP_PORT'] %>
  pool: 5
  timeout: 5000
  template: template0

# Start a database container
docker run --name $DATABASE_CONTAINER_NAME -d postgres

# Start the app container
docker run --name $APP_CONTAINER_NAME -v /local_src_directory:/home/app/app_name --link $DATABASE_CONTAINER_NAME:postgres -d $APP_IMAGE_NAME

This gives you a database connection, but you'll still need to run rake db:setup or similar during startup to create and seed your DB.

from passenger-docker.

Thanks for your answer, I'm also using a separate container for the Postgres Database.
Your answer contains several useful hints to get me further.
But i was able to find the root of the problem by now.

The following should find its way into the Readme:

You have to do an apt-get update when using the images; e.g:

FROM phusion/passenger-full:0.9.11
ENV HOME /root
CMD ["/sbin/my_init"]

RUN apt-get update
...continue here

from passenger-docker.

@danielkummer I don't believe the full image includes dev headers, and yeah, you're right, you need to run apt-get update first or you'll try to pull old packages that don't exist anymore.

RUN apt-get update -qq
RUN /build/devheaders.sh

from passenger-docker.

@skord it works with the passenger-full image (even the devheaders) but it doesn't seem to work with passenger-customizable (which it should in my opinion)

from passenger-docker.

Probably a bug in passenger-customizable. I'll have a look once I have time.

from passenger-docker.