trying to build local unms controller: ./install-full.sh fails to set postgres user password

[arielf]

My environment is a plain Ubuntu 18.04.4 LTS with dockerio, docker-compose, etc. installed.

I'm following the instructions in: https://help.ubnt.com/hc/en-us/articles/115012196527-UNMS-Installation-Guide

• 1st stage works fine. It downloads the unms_inst.sh script and runs it.
• 2nd stage, running the downloaded ./install-full.sh script, manages to download all the docker images and compose most of the environment, but fails when trying to change the container postgres user password.

Failure session details

% curl -fsSL https://unms.com/v1/install > /tmp/unms_inst.sh && sudo bash /tmp/unms_inst.sh
branch=master
version=1.1.6
Downloading installation package for version 1.1.6.
Setting VERSION=1.1.6
Docker version: 19.03.6
Docker Compose version: 1.9
Skipping vm.overcommit_memory setting. Server has enough memory.
Skipping 0.8.0 permission fix
Creating data volumes.
Will mount /home/unms/data
Creating docker-compose.yml
Pulling docker images.
Pulling fluentd (ubnt/unms-fluentd:1.1.6)...
1.1.6: Pulling from ubnt/unms-fluentd
Digest: sha256:a0bfeea2ceb26a85a682ced00646c831b9894c4995a42a6685ee001a0ccd5bfc
Status: Image is up to date for ubnt/unms-fluentd:1.1.6
Pulling postgres (postgres:9.6.12-alpine)...
9.6.12-alpine: Pulling from library/postgres
Digest: sha256:a7fe157e12a492fae58d10fe102c437b9e71ae911592a5ca4022181b921f0262
Status: Image is up to date for postgres:9.6.12-alpine
Pulling redis (redis:5.0.5-alpine)...
5.0.5-alpine: Pulling from library/redis
Digest: sha256:50899ea1ceed33fa03232f3ac57578a424faa1742c1ac9c7a7bdb95cdf19b858
Status: Image is up to date for redis:5.0.5-alpine
Pulling rabbitmq (rabbitmq:3.7.14-alpine)...
3.7.14-alpine: Pulling from library/rabbitmq
Digest: sha256:bdad3112d864950971278d5690daea39d20c31b959ec58a9d2022ec4e2ae90d9
Status: Image is up to date for rabbitmq:3.7.14-alpine
Pulling nginx (ubnt/unms-nginx:1.1.6)...
1.1.6: Pulling from ubnt/unms-nginx
Digest: sha256:7a2bfbf15c551369d3da871898ac34f53c898ce5464fe54157cfcf920c437fef
Status: Image is up to date for ubnt/unms-nginx:1.1.6
Pulling netflow (ubnt/unms-netflow:1.1.6)...
1.1.6: Pulling from ubnt/unms-netflow
Digest: sha256:3d5694433ce954ba4c8ce62b88b1d36d0d0ccbe91cf523bd65052da67807a21c
Status: Image is up to date for ubnt/unms-netflow:1.1.6
Pulling ucrm (ubnt/unms-crm:3.1.6)...
3.1.6: Pulling from ubnt/unms-crm
Digest: sha256:8b53cf92f77489a65f983c3c54403adad7ce08fb898c61f7b0db96806ed4a287
Status: Image is up to date for ubnt/unms-crm:3.1.6
Pulling unms (ubnt/unms:1.1.6)...
1.1.6: Pulling from ubnt/unms
Digest: sha256:10c7f1de7d8901b9b6a10f150112f3338efff94b300d329fd73f02dd28f618b4
Status: Image is up to date for ubnt/unms:1.1.6
Using default tag: latest
latest: Pulling from ubnt/ucrm-conntrack
Digest: sha256:5ed724152a396c413db84cdb412146d9f2f655a2ef96ed45b26e4d2e2c4ebee3
Status: Image is up to date for ubnt/ucrm-conntrack:latest
docker.io/ubnt/ucrm-conntrack:latest
Stopping docker containers.
Stopping unms ... done
Stopping unms-netflow ... done
Stopping ucrm ... done
Stopping unms-nginx ... done
Stopping unms-postgres ... done
Stopping unms-rabbitmq ... done
Stopping unms-redis ... done
Stopping unms-fluentd ... done
Removing unms ... done
Removing unms-netflow ... done
Removing ucrm ... done
Removing unms-nginx ... done
Removing unms-postgres ... done
Removing unms-rabbitmq ... done
Removing unms-redis ... done
Removing unms-fluentd ... done
Removing network unms_internal
Removing network unms_public
File capabilities are supported.
Checking available ports
Port 80 is already in use, please choose a different HTTP port for UNMS. [8080]: 
Port 8080/tcp is free.
Port 443/tcp is free.
Port 81/tcp is free.
Port 2055/udp is free.
Creating docker-compose.yml
Deploying templates
Starting postgres DB.
Creating network "unms_internal" with the default driver
Creating network "unms_public" with the default driver
Creating unms-fluentd
Creating unms-postgres
Updating Postgres DB passwords.
ERROR: Failed to update password for user 'postgres'...

The postgres user is inside the docker container, so the process should have full control of it.

[kkhanh]

Hi,

Same problem. Have you found a workaround ?

[arielf]

Sorry no. I gave up on the device, returned it, and bought something that just works out of the box.