[GH-ISSUE #1369] [BUG] Dockerfile Build Fails #477

Closed
opened 2026-02-27 08:17:28 +03:00 by kerem · 3 comments
Owner

Originally created by @vividnightmare on GitHub (Dec 24, 2025).
Original GitHub issue: https://github.com/lldap/lldap/issues/1369

Describe the bug
Building the image locally using release zip v0.6.2 on arm64 ubuntu using podman 4.9.3.

Build fails at the step
RUN cargo build --release -p lldap -p lldap_migration_tool -p lldap_set_password
# Build the frontend.
&& ./app/build.sh

with error
[INFO]: Installing wasm-bindgen...
Error: No such file or directory (os error 2)
Caused by: No such file or directory (os error 2)
gzip: pkg/lldap_app_bg.wasm: No such file or directory
Error: building at STEP "RUN cargo build --release -p lldap -p lldap_migration_tool -p lldap_set_password && ./app/build.sh": while running runtime: exit status 1

To Reproduce
Steps to reproduce the behavior:

  1. Download and extract 0.6.2 zip from github releases on ubuntu 24.04 arm.
  2. Change to extracted directory and build container image
  3. podman build -t lldap .
  4. Wait for a while....
  5. Build fails with above error.
    Expected behavior
    Expect build to succeed and a local image to be available.

Logs
It's far too long to paste here, see the above error.

Additional context
ubuntu 24.04 arm64
podman 4.9.3
rootless quadlet (intended)

Originally created by @vividnightmare on GitHub (Dec 24, 2025). Original GitHub issue: https://github.com/lldap/lldap/issues/1369 **Describe the bug** Building the image locally using release zip v0.6.2 on arm64 ubuntu using podman 4.9.3. Build fails at the step RUN cargo build --release -p lldap -p lldap_migration_tool -p lldap_set_password \ # Build the frontend. && ./app/build.sh with error [INFO]: Installing wasm-bindgen... Error: No such file or directory (os error 2) Caused by: No such file or directory (os error 2) gzip: pkg/lldap_app_bg.wasm: No such file or directory Error: building at STEP "RUN cargo build --release -p lldap -p lldap_migration_tool -p lldap_set_password && ./app/build.sh": while running runtime: exit status 1 **To Reproduce** Steps to reproduce the behavior: 1. Download and extract 0.6.2 zip from github releases on ubuntu 24.04 arm. 2. Change to extracted directory and build container image 3. `podman build -t lldap .` 4. Wait for a while.... 5. Build fails with above error. **Expected behavior** Expect build to succeed and a local image to be available. **Logs** It's far too long to paste here, see the above error. **Additional context** ubuntu 24.04 arm64 podman 4.9.3 rootless quadlet (intended)
kerem 2026-02-27 08:17:28 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@coderabbitai[bot] commented on GitHub (Dec 24, 2025):

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

  • Create Plan
Examples

🔗 Similar Issues

Related Issues

👤 Suggested Assignees

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

<!-- gh-comment-id:3688687197 --> @coderabbitai[bot] commented on GitHub (Dec 24, 2025): <!-- This is an auto-generated issue plan by CodeRabbit --> ### 📝 CodeRabbit Plan Mode Generate an implementation plan and prompts that you can use with your favorite coding agent. - [ ] <!-- {"checkboxId": "8d4f2b9c-3e1a-4f7c-a9b2-d5e8f1c4a7b9"} --> Create Plan <details> <summary>Examples</summary> - [Example 1](https://github.com/coderabbitai/git-worktree-runner/issues/29#issuecomment-3589134556) - [Example 2](https://github.com/coderabbitai/git-worktree-runner/issues/12#issuecomment-3606665167) </details> --- <details> <summary><b>🔗 Similar Issues</b></summary> **Related Issues** - https://github.com/lldap/lldap/issues/1184 - https://github.com/lldap/lldap/issues/1206 - https://github.com/lldap/lldap/issues/1220 - https://github.com/lldap/lldap/issues/1290 - https://github.com/lldap/lldap/issues/1304 </details> <details> <summary><b>👤 Suggested Assignees</b></summary> - [Pierre-Lannoy](https://github.com/Pierre-Lannoy) - [BerkhanBerkdemir](https://github.com/BerkhanBerkdemir) - [selfhoster1312](https://github.com/selfhoster1312) - [vic1707](https://github.com/vic1707) - [hungrymonkey](https://github.com/hungrymonkey) </details> --- <details> <summary> 🧪 Issue enrichment is currently in open beta.</summary> You can configure auto-planning by selecting labels in the issue_enrichment configuration. To disable automatic issue enrichment, add the following to your `.coderabbit.yaml`: ```yaml issue_enrichment: auto_enrich: enabled: false ``` </details> 💬 Have feedback or questions? Drop into our [discord](https://discord.gg/coderabbit) or [schedule a call](https://calendly.com/parth-coderabbit/issues-feedback)!
Author
Owner

@nitnelave commented on GitHub (Dec 24, 2025):

The root dockerfile is always a bit outdated (we should have CI to test it), it's a dev container. The one used to produce the images we publish is in .github/workflows

<!-- gh-comment-id:3689139862 --> @nitnelave commented on GitHub (Dec 24, 2025): The root dockerfile is always a bit outdated (we should have CI to test it), it's a dev container. The one used to produce the images we publish is in .github/workflows
Author
Owner

@vividnightmare commented on GitHub (Dec 24, 2025):

Thanks, I'll try that one this afternoon.

<!-- gh-comment-id:3690118454 --> @vividnightmare commented on GitHub (Dec 24, 2025): Thanks, I'll try that one this afternoon.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/lldap-lldap#477
No description provided.