Skip to content

ci: set BB_HASHSERVE_DB_DIR to local path (avoid EFS/NFS error) - #16628

Merged
rpcme merged 1 commit into
master-nextfrom
fix/hashserv-db-dir
Aug 10, 2026
Merged

rpcme merged 1 commit into
master-nextfrom
fix/hashserv-db-dir

Conversation

@rpcme

@rpcme rpcme commented Aug 10, 2026

Copy link
Copy Markdown
Member

Problem

BB_HASHSERVE = "auto" starts a local hash equivalency server but still needs a sqlite database on disk. BB_HASHSERVE_DB_DIR defaults to SSTATE_DIR which is /sstate-cache — an AWS EFS mount (NFS protocol). Bitbake rejects this:

ERROR: Hash equivalency database location (set via BB_HASHSERVE_DB_DIR to /sstate-cache)
cannot be on a NFS mount due to potential NFS locking issues between sqlite clients

Fix

Set BB_HASHSERVE_DB_DIR = "/tmp/hashserv-db" which is always local to the CodeBuild runner instance.

This applies to both internal and fork PRs — the NFS mount issue is a property of the CI runner environment, not the GitHub security context.

Unblocks #16292.

BB_HASHSERVE=auto starts a local hash equivalency server, but it
still needs a sqlite DB on disk. BB_HASHSERVE_DB_DIR defaults to
SSTATE_DIR (/sstate-cache) which is EFS (NFS protocol), causing:

  ERROR: Hash equivalency database location (BB_HASHSERVE_DB_DIR)
  cannot be on a NFS mount

Fix: explicitly set BB_HASHSERVE_DB_DIR=/tmp/hashserv-db which is
always local to the CodeBuild runner instance.
@rpcme
rpcme requested a review from a team as a code owner August 10, 2026 12:47
@rpcme
rpcme merged commit 7eb3304 into master-next Aug 10, 2026
6 of 10 checks passed
@rpcme
rpcme deleted the fix/hashserv-db-dir branch August 10, 2026 12:47
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