Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to start vault agent (version 1.18.0) in Windows #28734

Closed
esenmarti opened this issue Oct 18, 2024 · 1 comment · Fixed by #28748
Closed

Unable to start vault agent (version 1.18.0) in Windows #28734

esenmarti opened this issue Oct 18, 2024 · 1 comment · Fixed by #28748
Labels
agent bug Used to indicate a potential bug reproduced This issue has been reproduced by a Vault engineer

Comments

@esenmarti
Copy link

Describe the bug
Creating a vault agent in Windows with the new 1.18.0 version fails with error creating file sink: error during write check: error changing ownership of XXX: chown XXX: not supported by windows

To Reproduce
vault.exe agent -config="config.hcl"

Expected behavior
The vault agent starts (this is what we see in the same env when using 1.17.6)

Environment:

  • Vault Server Version (retrieve with vault status): 1.15.4
  • Vault CLI Version (retrieve with vault version): Vault v1.18.0 (77f26ba), built 2024-10-08T09:12:52Z
  • Server Operating System/Architecture: Windows

Vault server configuration file(s):

exit_after_auth = true
pid_file = "/vault/pidfile"

vault {
  address = "xxx"
  retry {
    num_retries = 5
  }
}

auto_auth {
  method "gcp" {
    exit_on_err = true
    mount_path = "auth/xxx"
    config = {
      role = "xxx"
      type = "xx"

    }
  }

  sink "file" {
    config = {
      path = "/a/path/"
    }
  }
}

Additional context
It might have been introduced in #27123

@miagilepner miagilepner added bug Used to indicate a potential bug agent reproduced This issue has been reproduced by a Vault engineer labels Oct 21, 2024
@miagilepner
Copy link
Contributor

Thank you for reporting this! I've reproduced the issue and am working on the fix now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agent bug Used to indicate a potential bug reproduced This issue has been reproduced by a Vault engineer
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants