miko3ed

Following some of the info in the github issue I added three variables to the docker container (see attached img) and it fixed the environment allowing mylar to start back up. Just thought I'd try and help others here

That was it, Thanks!

getting the following after the docker installs: *** Running /etc/my_init.d/001-fix-the-time.sh... Current default time zone: 'America/New_York' Local time is now: Sat Jun 6 16:41:12 EDT 2015. Universal Time is now: Sat Jun 6 20:41:12 UTC 2015. *** Running /etc/my_init.d/002-configure-DBDefs.sh... DBDefs is in your config folder, may need editing *** Running /etc/my_init.d/003-postgres-initialise.sh... The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale "en_US.UTF-8". The default database encoding has accordingly been set to "UTF8". The default text search configuration will be set to "english". Data page checksums are disabled. fixing permissions on existing directory /data/main ... ok creating subdirectories ... ok selecting default max_connections ... 100 selecting default shared_buffers ... 128MB selecting dynamic shared memory implementation ... posix creating configuration files ... ok LOG: could not link file "pg_xlog/xlogtemp.42" to "pg_xlog/000000010000000000000001" (initialization of log file): Function not implemented FATAL: could not open file "pg_xlog/000000010000000000000001": No such file or directory child process exited with exit code 1 initdb: removing contents of data directory "/data/main" creating template1 database in /data/main/base/1 ... 2015-06-06 16:41:18,033 CRIT Supervisor running as root (no user in config file) 2015-06-06 16:41:18,034 INFO supervisord started with pid 44 2015-06-06 16:41:19,036 INFO spawned: 'redis-server' with pid 48 2015-06-06 16:41:19,037 INFO spawned: 'postgres' with pid 49 2015-06-06 16:41:19,041 INFO exited: postgres (exit status 2; not expected) 2015-06-06 16:41:20,042 INFO success: redis-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-06-06 16:41:20,043 INFO spawned: 'postgres' with pid 52 2015-06-06 16:41:20,047 INFO exited: postgres (exit status 2; not expected) 2015-06-06 16:41:22,050 INFO spawned: 'postgres' with pid 53 2015-06-06 16:41:22,054 INFO exited: postgres (exit status 2; not expected) 2015-06-06 16:41:25,058 INFO spawned: 'postgres' with pid 54 2015-06-06 16:41:25,062 INFO exited: postgres (exit status 2; not expected) 2015-06-06 16:41:26,063 INFO gave up: postgres entered FATAL state, too many start retries too quickly BEGINNING INITIAL DATABASE IMPORT ROUTINE, THIS COULD TAKE SEVERAL HOURS AND THE DOCKER MAY LOOK UNRESPONSIVE DO NOT STOP DOCKER UNTIL IT IS COMPLETED

having some issues with this, do I need to have a separate postgres instance running on the server already for this docker to work?

I had to swap connection to host, save, and then back to bridge as well. Haven't rebooted yet. DNS resolution is fine at the command line and with plugins, it's just my dockers that had the issue