"address already in use" on starting PostgreSQL

[Irio]

When I try to start provisioning a machine, I get the following message and a non successful exit status:

2014/06/01 01:08:27 Error: Cannot start container 14cfb8e3b59f4c3e4682e2249cff8277f63e42cba440d02a04bf7605aa3f5576: listen tcp 0.0.0.0:5432: bind: address already in use

Complete log follows:
https://gist.github.com/Irio/80fefb95f0a35abb6a3d

Am I able to change port of services?

[ndrluis]

I think do you have a problem with forward port.

try shutdown the host postgresql service or add forward_port[5432, 5433] in Vagrantfile

[fgrehm]

@Irio can you please vagrant ssh into the VM, run docker ps -a, docker images and post the output over here? A gist with the whole output of a vagrant up --debug from scratch would also be great. Thanks in advance!

[Irio]

@andreanastacio Not sure if this is a problem with the host, since my PostgreSQL instance is down when trying to get the vm running. Maybe postgres-9.3 and postgresql-contrib conflict when starting the service.

@fgrehm Just updated the gist with the asked info.

[fgrehm]

@Irio weird, somehow docker created a container for a image that it wasn't able to download completely oO I'm not sure it is related but you might be experiencing those issues because ventriloquist locks the docker version to a known to work one.

Maybe you can try using the :latest docker version as explained on https://github.com/fgrehm/ventriloquist#usage to see if it works?

[Irio]

With the latest version of docker worked properly. Thanks, @fgrehm.