search

Websoft9 / docker-library

Docker Compose examples of selfhosted FOSS based on official image, just run it.
https://www.websoft9.com
Other
36 stars 25 forks source link

Update version to [1.18] for [vault] 10￥ #829

Closed qiaofeng1227 closed 2 weeks ago

qiaofeng1227 commented 2 weeks ago

What type of your feature request?

Change the W9_VERSION to target version number at .env and test it

Research and development steps your need to do

How to commit your change to docker-library? 

   docker exec -it websoft9-apphub bash
   apphub subimt --appid --github_token

Testing steps

cbnb233 commented 2 weeks ago

docker logs vault_naw1j:

==> Vault server configuration:
Administrative Namespace: 
             Api Address: http://0.0.0.0:8200
                     Cgo: disabled
         Cluster Address: https://0.0.0.0:8201
   Environment Variables: GOTRACEBACK, HOME, HOSTNAME, NAME, PATH, PWD, SHLVL, VAULT_LOCAL_CONFIG, VERSION, W9_APP_NAME, W9_DIST, W9_HTTP_PORT, W9_HTTP_PORT_SET, W9_ID, W9_LOGIN_GET_TOKEN, W9_NETWORK, W9_REPO, W9_URL, W9_VERSION
              Go Version: go1.22.8
              Listener 1: tcp (addr: "0.0.0.0:8200", cluster address: "0.0.0.0:8201", disable_request_limiter: "false", max_request_duration: "1m30s", max_request_size: "33554432", tls: "disabled")
               Log Level: 
                   Mlock: supported: true, enabled: false
           Recovery Mode: false
                 Storage: inmem
                 Version: Vault v1.18.1, built 2024-10-29T14:21:31Z
             Version Sha: f479e5c85462477c9334564bc8f69531cdb03b65
==> Vault server started! Log data will stream in below:
2024-11-01T00:59:37.286Z [INFO]  proxy environment: http_proxy="" https_proxy="" no_proxy=""
2024-11-01T00:59:37.286Z [INFO]  incrementing seal generation: generation=1
2024-11-01T00:59:37.286Z [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
2024-11-01T00:59:37.286Z [INFO]  core: Initializing version history cache for core
2024-11-01T00:59:37.286Z [INFO]  events: Starting event system
2024-11-01T00:59:37.287Z [INFO]  core: security barrier not initialized
2024-11-01T00:59:37.287Z [INFO]  core: security barrier initialized: stored=1 shares=1 threshold=1
2024-11-01T00:59:37.288Z [INFO]  core: post-unseal setup starting
2024-11-01T00:59:37.298Z [INFO]  core: loaded wrapping token key
2024-11-01T00:59:37.298Z [INFO]  core: successfully setup plugin runtime catalog
2024-11-01T00:59:37.298Z [INFO]  core: successfully setup plugin catalog: plugin-directory=""
2024-11-01T00:59:37.298Z [INFO]  core: no mounts; adding default mount table
2024-11-01T00:59:37.299Z [INFO]  core: successfully mounted: type=cubbyhole version="v1.18.1+builtin.vault" path=cubbyhole/ namespace="ID: root. Path: "
2024-11-01T00:59:37.300Z [INFO]  core: successfully mounted: type=system version="v1.18.1+builtin.vault" path=sys/ namespace="ID: root. Path: "
2024-11-01T00:59:37.300Z [INFO]  core: successfully mounted: type=identity version="v1.18.1+builtin.vault" path=identity/ namespace="ID: root. Path: "
2024-11-01T00:59:37.302Z [INFO]  core: successfully mounted: type=token version="v1.18.1+builtin.vault" path=token/ namespace="ID: root. Path: "
2024-11-01T00:59:37.302Z [INFO]  rollback: Starting the rollback manager with 256 workers
2024-11-01T00:59:37.302Z [INFO]  rollback: starting rollback manager
2024-11-01T00:59:37.302Z [INFO]  core: restoring leases
2024-11-01T00:59:37.302Z [INFO]  expiration: lease restore complete
2024-11-01T00:59:37.302Z [INFO]  identity: entities restored
2024-11-01T00:59:37.303Z [INFO]  identity: groups restored
2024-11-01T00:59:37.303Z [INFO]  core: Recorded vault version: vault version=1.18.1 upgrade time="2024-11-01 00:59:37.303078858 +0000 UTC" build date=2024-10-29T14:21:31Z
2024-11-01T00:59:37.303Z [INFO]  core: post-unseal setup complete
2024-11-01T00:59:37.303Z [INFO]  core: root token generated
2024-11-01T00:59:37.303Z [INFO]  core: pre-seal teardown starting
2024-11-01T00:59:37.303Z [INFO]  rollback: stopping rollback manager
2024-11-01T00:59:37.303Z [INFO]  core: pre-seal teardown complete
2024-11-01T00:59:37.304Z [INFO]  core.cluster-listener.tcp: starting listener: listener_address=0.0.0.0:8201
2024-11-01T00:59:37.304Z [INFO]  core.cluster-listener: serving cluster requests: cluster_listen_address=[::]:8201
2024-11-01T00:59:37.304Z [INFO]  core: post-unseal setup starting
2024-11-01T00:59:37.304Z [INFO]  core: loaded wrapping token key
2024-11-01T00:59:37.304Z [INFO]  core: successfully setup plugin runtime catalog
2024-11-01T00:59:37.304Z [INFO]  core: successfully setup plugin catalog: plugin-directory=""
2024-11-01T00:59:37.304Z [INFO]  core: successfully mounted: type=system version="v1.18.1+builtin.vault" path=sys/ namespace="ID: root. Path: "
2024-11-01T00:59:37.305Z [INFO]  core: successfully mounted: type=identity version="v1.18.1+builtin.vault" path=identity/ namespace="ID: root. Path: "
2024-11-01T00:59:37.305Z [INFO]  core: successfully mounted: type=cubbyhole version="v1.18.1+builtin.vault" path=cubbyhole/ namespace="ID: root. Path: "
2024-11-01T00:59:37.305Z [INFO]  core: successfully mounted: type=token version="v1.18.1+builtin.vault" path=token/ namespace="ID: root. Path: "
2024-11-01T00:59:37.305Z [INFO]  rollback: Starting the rollback manager with 256 workers
2024-11-01T00:59:37.305Z [INFO]  rollback: starting rollback manager
2024-11-01T00:59:37.306Z [INFO]  core: restoring leases
2024-11-01T00:59:37.306Z [INFO]  identity: entities restored
2024-11-01T00:59:37.306Z [INFO]  identity: groups restored
2024-11-01T00:59:37.306Z [INFO]  expiration: lease restore complete
2024-11-01T00:59:37.306Z [INFO]  core: post-unseal setup complete
2024-11-01T00:59:37.306Z [INFO]  core: vault is unsealed
2024-11-01T00:59:37.309Z [INFO]  core: successful mount: namespace="" path=secret/ type=kv version="v0.20.0+builtin"
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 variables:
    $ 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: k/SbAvKEIUwhNPTH64gxGtuuHuh6pdTE/JalosAYKi4=
Root Token: hvs.ymG6Av7xzYguSta9zGFsRrI4
Development mode should NOT be used in production installations!

image