can not start opencode on ubuntu /tmp does not allow execution of .so #5175

Activity

1. falko-apheris

   added

   bugSomething isn't workingSomething isn't working

   on Dec 6, 2025
2. github-actions

   added

   opentuiThis relates to changes in v1.0, now that opencode uses opentuiThis relates to changes in v1.0, now that opencode uses opentui

   on Dec 6, 2025
3. github-actions commented on Dec 6, 2025

   

   github-actionsBot

   on Dec 6, 2025 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • [FEATURE]: allow /tmp or $TMPDIR folder access option #4743: [FEATURE]: allow /tmp or $TMPDIR folder access option

   This is a feature request to allow write access to /tmp or specify a custom TMPDIR, which would address the security hardening issue you're experiencing on Ubuntu. Feel free to ignore if your specific case requires a different solution.
4. falko-apheris commented on Dec 6, 2025

   

   falko-apheris

   on Dec 6, 2025

   Author

   More actions

   follwing the link of the actions box, I found a fix

   BUN_TMPDIR=~/.opencode/tmp opencode --print-logs --log-level DEBUG    
   

   I would still wish that opencode would work out of the box
5. rekram1-node

   assigned

   kommander

   on Dec 10, 2025
6. kommander commented on Dec 20, 2025

   

   kommander

   on Dec 20, 2025 – with Linear

   Contributor

   More actions

   It is a bun issue that is being worked on.
7. jpcaparas commented on Jan 14, 2026

   

   jpcaparas

   on Jan 14, 2026

   More actions

   For *nix users having this issue, here's a drop-in wrapper command based on this answer:

   opencode() {
       local tmpdir="$HOME/.opencode/tmp"
       mkdir -p "$tmpdir"
       BUN_TMPDIR="$tmpdir" command opencode "$@"
   }

   👍React with 👍2Reacted by lolikung and koen-dejonghe-vdab
8. thdxr commented on Mar 25, 2026

   

   thdxr

   on Mar 25, 2026

   Member

   More actions

   To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
9. thdxr

   closed this as completedon Mar 25, 2026
10. nkedel commented on May 11, 2026

    

    nkedel

    on May 11, 2026

    More actions

    Issue is not just Ubuntu:

    Add me to the bunch of users who are hitting this issue; I've worked around it, but here's gemini helping me describe what I hit:

    Title: [Bug] Indefinite hang on startup when /tmp is mounted noexec (WSL/Hardened Linux)
    Description:
    On systems where /tmp is mounted with the noexec flag (common in WSL and hardened Linux environments), opencode hangs indefinitely during the initialization of the OpenTUI render library.
    Behavior Analysis:
    Tracing the process via strace shows that the main process and its child enter an infinite loop of thread synchronization attempts (a "futex storm"). The logs confirm that OpenTUI fails to map its native library from /tmp because of the noexec restriction:

    ERROR service=default e=Failed to initialize OpenTUI render library:
    Failed to open library "/tmp/.7bef6dbfdf7f5fbd-00000001.so":
    failed to map segment from shared object rejection

    Instead of exiting with a fatal error, the process blocks indefinitely on an epoll_pwait2 call, waiting for an event from a native worker that never successfully initialized.
    Steps to Reproduce:

    1. Mount /tmp with noexec (e.g., sudo mount -o remount,noexec /tmp).
    2. Run opencode.
    3. The process will hang silently with high CPU usage or indefinite blocking.

    Workaround:
    Directing temporary file extraction to a location with execution permissions resolves the issue:
    export TMPDIR=~/tmp && opencode
    Technical Environment:

    • OS: WSL / Gentoo (defaults)
    • Node Version: v24.15.0 (LTS)
    • Opencode Version: 1.14.48

    Suggested Fix:

    • The application should detect if library mapping fails and exit with a clear error message.
    • Ideally, OpenTUI should respect TMPDIR consistently or use a more standard, non-temporary path for its native binary components.