Github messages for voidlinux
 help / color / mirror / Atom feed
From: FatmanUK <FatmanUK@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Vault UI is not available in this binary.
Date: Thu, 02 Sep 2021 22:01:35 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32807@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

New issue by FatmanUK on void-packages repository

https://github.com/void-linux/void-packages/issues/32807

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
$ xuname
Void 5.3.9_1 x86_64 GenuineIntel notuptodate rrrrmmnFFFFFFFFF

$ xbps-query -p pkgver vault
vault-1.8.1_1

### Expected behavior
Web UI loads.

### Actual behavior
Error: "Vault UI is not available in this binary."

### Steps to reproduce the behavior
\# xbps-install vault
Follow Hashicorp tutorial to learn Vault and start the service.
Connect to localhost:8200 with curl or Chromium.

Similar issues:
https://github.com/Homebrew/brew/issues/7614 (but I'm not using homebrew, I'm using server mode and I unsealed manually)
https://discuss.hashicorp.com/t/official-hashicorp-tap-for-homebrew/4327 (again not using homebrew)

I'm trying to fork the package but I have a lot of learning to do about go packages. I'm hoping you'll be able to fix this trivially.

             reply	other threads:[~2021-09-02 20:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02 20:01 FatmanUK [this message]
2021-09-03  0:50 ` ericonr
2021-10-21 17:30 ` FatmanUK
2021-10-21 21:35 ` FatmanUK
2021-10-21 21:36 ` FatmanUK
2022-06-05  2:14 ` github-actions
2022-06-19  2:15 ` [ISSUE] [CLOSED] " github-actions

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32807@inbox.vuxu.org \
    --to=fatmanuk@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).