# Installing v0.9.1 not working

**URL:** <https://discuss.hashicorp.com/t/installing-v0-9-1-not-working/41768>\
**Category:** Boundary\
**Created:** [July 8, 2022, 3:50pm UTC](https://discuss.hashicorp.com/t/installing-v0-9-1-not-working/41768 "2022-07-08T15:50:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cten](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/cten/32/1857_2.png) [@cten](https://discuss.hashicorp.com/u/cten)\
**Post date:** [July 8, 2022, 3:50pm UTC](https://discuss.hashicorp.com/t/installing-v0-9-1-not-working/41768/1 "2022-07-08T15:50:49Z")

</div>

When I initialize the db, based on the logs it looks successful

```auto
Migrations successfully run.
Global-scope KMS keys successfully created.

Initial login role information:
  Name: Login and Default Grants
  Role ID: r_I91S23dofu

```

But when I start the server it complains that the db hasn’t been initialized and logs this

```auto
{"id":"h28YSorKT1","source":"https://hashicorp.com/boundary/boundary-db47d549b-rcdb7/boundary-database-init","specversion":"1.0","type":"error","data":{"error":"postgres.(Postgres).EnsureVersionTable: unknown, unknown: error #0: ERROR: relation \"boundary_schema_version\" already exists (SQLSTATE 42P07)","error_fields":{"Code":0,"Msg":"","Op":"postgres.(Postgres).EnsureVersionTable","Wrapped":{"Severity":"ERROR","Code":"42P07","Message":"relation \"boundary_schema_version\" already exists","Detail":"","Hint":"","Position":0,"InternalPosition":0,"InternalQuery":"","Where":"","SchemaName":"","TableName":"","ColumnName":"","DataTypeName":"","ConstraintName":"","File":"heap.c","Line":1182,"Routine":"heap_create_with_catalog"}},"id":"e_HBaMjs7Emq","version":"v0.1","op":"postgres.(Postgres).EnsureVersionTable"},"datacontentype":"application/cloudevents","time":"2022-07-08T15:34:54.152029362Z"}

```

---

<div class="post-metadata">

**Author:** ![jimlambrt](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/jimlambrt/32/12946_2.png) [@jimlambrt](https://discuss.hashicorp.com/u/jimlambrt)\
**Post date:** [July 8, 2022, 5:34pm UTC](https://discuss.hashicorp.com/t/installing-v0-9-1-not-working/41768/2 "2022-07-08T17:34:33Z")

</div>

Based on the `source` of the event being `boundary-database-init` and the Postgres 42P07 error, it looks like you’re trying to init the database again.

---

<div class="post-metadata">

**Author:** ![cten](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/cten/32/1857_2.png) [@cten](https://discuss.hashicorp.com/u/cten)\
**Post date:** [July 8, 2022, 8:09pm UTC](https://discuss.hashicorp.com/t/installing-v0-9-1-not-working/41768/3 "2022-07-08T20:09:35Z")

</div>

I am running this inside a container with this command:

```auto
boundary database migrate -config /boundary/config.hcl || boundary database init -config /boundary/config.hcl || sleep 1000

```

Maybe the migrate is failing? Does it exit with a different code than the previous versions?

---

<div class="post-metadata">

**Author:** ![jimlambrt](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/jimlambrt/32/12946_2.png) [@jimlambrt](https://discuss.hashicorp.com/u/jimlambrt)\
**Post date:** [July 10, 2022, 11:04pm UTC](https://discuss.hashicorp.com/t/installing-v0-9-1-not-working/41768/4 "2022-07-10T23:04:56Z")

</div>

🤔 you said earlier: “when I start a server it complains…” and then posted an error which can only come from the `boundary database init`

now, you’ve posted a set of OR’d commands which would attempt to migrate the db and if it fails, assume that the db hasn’t been initialized and attempt to init the db. But I don’t see the connection between these and the earlier “when I start a server…” that results in an init error.

Perhaps I’m don’t know enough about your deployment env.

---

<div class="post-metadata">

**Author:** ![cten](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/cten/32/1857_2.png) [@cten](https://discuss.hashicorp.com/u/cten)\
**Post date:** [July 14, 2022, 4:16pm UTC](https://discuss.hashicorp.com/t/installing-v0-9-1-not-working/41768/5 "2022-07-14T16:16:13Z")

</div>

I am trying to deploy into Kubernetes. With k8s you can specify an init-container that runs before the main process. I configured my deployment to run this command in the init-container `boundary database migrate -config /boundary/config.hcl || boundary database init -config /boundary/config.hcl || sleep 300`  
Then the main process starts with this command `boundary server -config /boundary/config.hcl`  
Both containers are sharing the volume with the config.hcl