Skip to content

fix(eso): force absolute Bitwarden DNS on OCI - #82

Merged
syscod3 merged 1 commit into
mainfrom
fix/oci-eso-absolute-bitwarden-dns
Sep 8, 2026
Merged

syscod3 merged 1 commit into
mainfrom
fix/oci-eso-absolute-bitwarden-dns

Conversation

@syscod3

@syscod3 syscod3 commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Force absolute Bitwarden API and Identity DNS lookups using trailing-dot URLs.
  • OCI ESO consistently received Identity HTTP 400 despite the valid shared machine token; the public Bitwarden SDK server issue documents this as CoreDNS search expansion returning empty NOERROR.
  • Revert the unsuccessful v0.7.0 image override to the vendored v0.6.0 default.

Validation

  • YAML parse/assertion for both absolute URLs
  • pre-commit run --files ...
  • comparable Unraid store inspection and upstream issue #4824 resolution.

@syscod3
syscod3 merged commit 49b0b70 into main Sep 8, 2026
5 checks passed
@syscod3
syscod3 deleted the fix/oci-eso-absolute-bitwarden-dns branch September 8, 2026 09:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant