docker file update command output

zamil@docker-test:~/Documents/docker-test/docker-gluu-server$ docker run \                                                           [50/4654]
>     -v vault_gluu_policy.hcl:/vault/config/policy.hcl \
>     vault:1.0.3
Couldn't start vault with IPC_LOCK. Disabling IPC_LOCK, please use --privileged or --cap-add IPC_LOCK
==> Vault server configuration:

             Api Address: http://0.0.0.0:8200
                     Cgo: disabled
         Cluster Address: https://0.0.0.0:8201
              Listener 1: tcp (addr: "0.0.0.0:8200", cluster address: "0.0.0.0:8201", max_request_duration: "1m30s", max_request_size: "335544
32", tls: "disabled")
               Log Level: info
                   Mlock: supported: true, enabled: false
                 Storage: inmem
                 Version: Vault v1.0.3
             Version Sha: 85909e3373aa743c34a6a0ab59131f61fd9e8e43

WARNING! dev mode is enabled! In this mode, Vault runs entirely in-memory
and starts unsealed with a single unseal key. The root token is already
authenticated to the CLI, so you can immediately begin using Vault.

You may need to set the following environment variable:

    $ export VAULT_ADDR='http://0.0.0.0:8200'

The unseal key and root token are displayed below in case you want to
seal/unseal the Vault or re-authenticate.

Unseal Key: VSqrxP06jHaGpw4RatlAKfPSpXhV7d3OCl5gubtDZgk=
Root Token: s.Of5gghvZF8BvM6P6FOQG2fdu

Development mode should NOT be used in production installations!

==> Vault server started! Log data will stream in below:
2019-05-17T15:53:24.869Z [WARN]  no `api_addr` value specified in config or in VAULT_API_ADDR; falling back to detection if possible, but this
 value should be manually set
2019-05-17T15:53:24.875Z [INFO]  core: security barrier not initialized
2019-05-17T15:53:24.875Z [INFO]  core: security barrier initialized: shares=1 threshold=1
2019-05-17T15:53:24.875Z [INFO]  core: post-unseal setup starting
2019-05-17T15:53:24.895Z [INFO]  core: loaded wrapping token key
2019-05-17T15:53:24.895Z [INFO]  core: successfully setup plugin catalog: plugin-directory=
2019-05-17T15:53:24.895Z [INFO]  core: no mounts; adding default mount table
2019-05-17T15:53:24.897Z [INFO]  core: successfully mounted backend: type=kv path=secret/
2019-05-17T15:53:24.897Z [INFO]  core: successfully mounted backend: type=cubbyhole path=cubbyhole/
2019-05-17T15:53:24.897Z [INFO]  core: successfully mounted backend: type=system path=sys/
2019-05-17T15:53:24.897Z [INFO]  core: successfully mounted backend: type=identity path=identity/
2019-05-17T15:53:24.899Z [INFO]  core: successfully enabled credential backend: type=token path=token/
2019-05-17T15:53:24.899Z [INFO]  core: restoring leases
2019-05-17T15:53:24.899Z [INFO]  rollback: starting rollback manager
2019-05-17T15:53:24.900Z [INFO]  expiration: lease restore complete
2019-05-17T15:53:24.900Z [INFO]  identity: entities restored
2019-05-17T15:53:24.900Z [INFO]  identity: groups restored
2019-05-17T15:53:24.900Z [INFO]  core: post-unseal setup complete
2019-05-17T15:53:24.900Z [INFO]  core: starting listener: listener_address=0.0.0.0:8201
2019-05-17T15:53:24.900Z [INFO]  core: serving cluster requests: cluster_listen_address=[::]:8201
2019-05-17T15:53:24.900Z [INFO]  core: root token generated
2019-05-17T15:53:24.901Z [INFO]  core: pre-seal teardown starting
2019-05-17T15:53:24.901Z [INFO]  core: stopping cluster listeners
2019-05-17T15:53:24.901Z [INFO]  core: shutting down forwarding rpc listeners
2019-05-17T15:53:24.901Z [INFO]  core: forwarding rpc listeners stopped
2019-05-17T15:53:25.401Z [INFO]  core: rpc listeners successfully shut down
2019-05-17T15:53:25.401Z [INFO]  core: cluster listeners successfully shut down
2019-05-17T15:53:25.401Z [INFO]  rollback: stopping rollback manager
2019-05-17T15:53:25.401Z [INFO]  core: pre-seal teardown complete
2019-05-17T15:53:25.401Z [INFO]  core: vault is unsealed
2019-05-17T15:53:25.401Z [INFO]  core: post-unseal setup starting
2019-05-17T15:53:25.401Z [INFO]  core: loaded wrapping token key
2019-05-17T15:53:25.401Z [INFO]  core: successfully setup plugin catalog: plugin-directory=
2019-05-17T15:53:25.402Z [INFO]  core: successfully mounted backend: type=kv path=secret/
2019-05-17T15:53:25.403Z [INFO]  core: successfully mounted backend: type=system path=sys/
2019-05-17T15:53:25.403Z [INFO]  core: successfully mounted backend: type=identity path=identity/
2019-05-17T15:53:25.403Z [INFO]  core: successfully mounted backend: type=cubbyhole path=cubbyhole/
2019-05-17T15:53:25.408Z [INFO]  core: successfully enabled credential backend: type=token path=token/
2019-05-17T15:53:25.408Z [INFO]  core: restoring leases
2019-05-17T15:53:25.408Z [INFO]  rollback: starting rollback manager
2019-05-17T15:53:25.408Z [INFO]  expiration: lease restore complete
2019-05-17T15:53:25.408Z [INFO]  identity: entities restored
2019-05-17T15:53:25.409Z [INFO]  identity: groups restored
2019-05-17T15:53:25.409Z [INFO]  core: post-unseal setup complete
2019-05-17T15:53:25.409Z [INFO]  core: starting listener: listener_address=0.0.0.0:8201
2019-05-17T15:53:25.409Z [INFO]  core: serving cluster requests: cluster_listen_address=[::]:8201
2019-05-17T15:53:25.411Z [INFO]  core: mount tuning of options: path=secret/ options=map[version:2]
2019-05-17T15:53:25.413Z [INFO]  secrets.kv.kv_f7774806: collecting keys to upgrade
2019-05-17T15:53:25.413Z [INFO]  secrets.kv.kv_f7774806: done collecting keys: num_keys=1
2019-05-17T15:53:25.413Z [INFO]  secrets.kv.kv_f7774806: upgrading keys finished