# Latest Boundary versions ignoring plugins execution\_dir

**URL:** <https://discuss.hashicorp.com/t/latest-boundary-versions-ignoring-plugins-execution-dir/41281>\
**Category:** Boundary\
**Created:** [June 27, 2022, 4:14pm UTC](https://discuss.hashicorp.com/t/latest-boundary-versions-ignoring-plugins-execution-dir/41281 "2022-06-27T16:14:55Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![raphaelschneider](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/raphaelschneider/32/29022_2.png) [@raphaelschneider](https://discuss.hashicorp.com/u/raphaelschneider)\
**Post date:** [June 27, 2022, 4:14pm UTC](https://discuss.hashicorp.com/t/latest-boundary-versions-ignoring-plugins-execution-dir/41281/1 "2022-06-27T16:14:55Z")

</div>

Hey everyone,

We use hardened images that have noexec set on /tmp mount, therefore we need to use another directory for plugins exec. That works fine on 0.7.5 - and so far I am locked in that version, because newer versions (apparently) ignore the setting altogether.  
The configuration is the same for both test cases, such as:

```auto
plugins {
  execution_dir = "/opt/boundary/plugin-exec"
}

```

With 0.7.5 the service start normally.  
With 0.9.0, though, it fails, with the same configuration, due to noexec on /tmp:

```auto

Jun 27 16:07:50 ip-10-237-99-241.eu-central-1.compute.internal systemd[1]: Started Access any system from anywhere based on user identity.
Jun 27 16:07:50 ip-10-237-99-241.eu-central-1.compute.internal boundary[10347]: Error parsing KMS configuration: error fetching kms plugin rpc client: fork/exec /tmp/3286585514/boundary-plugin-kms-awskms.gz: permission denied
Jun 27 16:07:50 ip-10-237-99-241.eu-central-1.compute.internal systemd[1]: boundary.service: main process exited, code=exited, status=3/NOTIMPLEMENTED
Jun 27 16:07:50 ip-10-237-99-241.eu-central-1.compute.internal systemd[1]: Unit boundary.service entered failed state.
Jun 27 16:07:50 ip-10-237-99-241.eu-central-1.compute.internal systemd[1]: boundary.service failed.

```

Can anyone tell me if I’m missing something please? Has the directive changed by any chance?

Many thanks

---

<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:** [June 27, 2022, 4:46pm UTC](https://discuss.hashicorp.com/t/latest-boundary-versions-ignoring-plugins-execution-dir/41281/2 "2022-06-27T16:46:38Z")

</div>

I think this was fixed in v0.9.0

> <https://github.com/hashicorp/boundary/pull/2183>
>
> \## \[fix: Propagate plugin options to CreatePlugin\](https://github.com/hashicorp/…boundary/pull/2183/commits/4fb90e069237a322af0fa8b74357d8d86a45f58d)
> 
> Plugin options were previously only applied to the
> BuildPluginMap call, resulting in the plugin
> execution\_dir variable being ineffective.
> 
> Also add a test to verify functionality
> 
> \## \[fix: Support plugin execution\_dir for all plugins\](https://github.com/hashicorp/boundary/pull/2183/commits/ae912db88c8802e05d1b5ff0d2169d07cdeee052)
> 
> Previously, only external host plugins would respect
> the plugin execution dir. Now, all uses of the embedded
> plugins respect the configuration.

> <https://github.com/hashicorp/boundary/blob/main/CHANGELOG.md#bug-fixes-1>

---

<div class="post-metadata">

**Author:** ![raphaelschneider](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/raphaelschneider/32/29022_2.png) [@raphaelschneider](https://discuss.hashicorp.com/u/raphaelschneider)\
**Post date:** [June 27, 2022, 5:06pm UTC](https://discuss.hashicorp.com/t/latest-boundary-versions-ignoring-plugins-execution-dir/41281/3 "2022-06-27T17:06:29Z")

</div>

Hi @jimlambrt,

Thanks for the reply.  
Unfortunately 0.9.0 still presents the same behaviour. I’ve tested it today…

Cheers

---

<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:** [June 27, 2022, 5:17pm UTC](https://discuss.hashicorp.com/t/latest-boundary-versions-ignoring-plugins-execution-dir/41281/4 "2022-06-27T17:17:13Z")

</div>

ty! I’ll let folks know.

---

<div class="post-metadata">

**Author:** ![jbrandhorst](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/jbrandhorst/32/45078_2.png) [@jbrandhorst](https://discuss.hashicorp.com/u/jbrandhorst)\
**Post date:** [June 27, 2022, 10:57pm UTC](https://discuss.hashicorp.com/t/latest-boundary-versions-ignoring-plugins-execution-dir/41281/5 "2022-06-27T22:57:04Z")

</div>

Just updating this topic to let you know that we’ve been able to reproduce this internally with the kms plugin. This regression appears to have been introduced in v0.8.0. We’ll try to get a fix out as soon as possible. Thanks for reporting the issue!

---

<div class="post-metadata">

**Author:** ![jeff](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/jeff/32/12882_2.png) [@jeff](https://discuss.hashicorp.com/u/jeff)\
**Post date:** [June 27, 2022, 11:10pm UTC](https://discuss.hashicorp.com/t/latest-boundary-versions-ignoring-plugins-execution-dir/41281/6 "2022-06-27T23:10:12Z")

</div>

The regression was introduced because when kms plugins were introduced in 0.8.0 they unfortunately weren’t set up to honor the execution dir the same way host plugins were. @johanbrandhorst has this fixed and it will go out in 0.9.1 as far as I know!

---

<div class="post-metadata">

**Author:** ![raphaelschneider](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/raphaelschneider/32/29022_2.png) [@raphaelschneider](https://discuss.hashicorp.com/u/raphaelschneider)\
**Post date:** [June 28, 2022, 8:52am UTC](https://discuss.hashicorp.com/t/latest-boundary-versions-ignoring-plugins-execution-dir/41281/7 "2022-06-28T08:52:34Z")

</div>

@jbrandhorst @jeff sounds good! Appreciate the update. Thanks a bunch!

---

<div class="post-metadata">

**Author:** ![jbrandhorst](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/jbrandhorst/32/45078_2.png) [@jbrandhorst](https://discuss.hashicorp.com/u/jbrandhorst)\
**Post date:** [June 28, 2022, 8:51pm UTC](https://discuss.hashicorp.com/t/latest-boundary-versions-ignoring-plugins-execution-dir/41281/8 "2022-06-28T20:51:56Z")

</div>

We have fixed this internally and will release the fix with v0.9.1. Thanks for your patience!

---

<div class="post-metadata">

**Author:** ![raphaelschneider](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/raphaelschneider/32/29022_2.png) [@raphaelschneider](https://discuss.hashicorp.com/u/raphaelschneider)\
**Post date:** [June 30, 2022, 8:46am UTC](https://discuss.hashicorp.com/t/latest-boundary-versions-ignoring-plugins-execution-dir/41281/10 "2022-06-30T08:46:00Z")

</div>

Thank you @jbrandhorst. Looking forward to it!

---

<div class="post-metadata">

**Author:** ![TaysirTayyab](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/taysirtayyab/32/29640_2.png) [@TaysirTayyab](https://discuss.hashicorp.com/u/TaysirTayyab)\
**Post date:** [July 22, 2022, 8:54pm UTC](https://discuss.hashicorp.com/t/latest-boundary-versions-ignoring-plugins-execution-dir/41281/11 "2022-07-22T20:54:41Z")

</div>

@jbrandhorst Just tried out 0.9.1 and this appears to still be an issue. Opened a bug here [Boundary Ignoring execution\_dir · Issue #2284 · hashicorp/boundary · GitHub](https://github.com/hashicorp/boundary/issues/2284)

---

<div class="post-metadata">

**Author:** ![TaysirTayyab](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/taysirtayyab/32/29640_2.png) [@TaysirTayyab](https://discuss.hashicorp.com/u/TaysirTayyab)\
**Post date:** [July 22, 2022, 9:00pm UTC](https://discuss.hashicorp.com/t/latest-boundary-versions-ignoring-plugins-execution-dir/41281/12 "2022-07-22T21:00:19Z")

</div>

Sorry ignore my last. Was running on 0.9.0. I apologize for the confusion.

Appears to be working correctly in 0.9.1
