OpenCode Attempts Package Installation on Startup Despite Auto-Update Being Disabled #7500

Open
opened 2026-02-16 18:07:22 -05:00 by yindo · 3 comments
Owner

Originally created by @suseemani on GitHub (Jan 24, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

I am attempting to start the container in a restricted environment that has access only to the LLM and no external network connectivity. To prevent automatic updates or package installations, I set the environment variable OPENCODE_DISABLE_AUTOUPDATE=1 when starting the container.

However, during startup, OpenCode still attempts to install packages. This behavior makes it difficult to run the container in environments with limited or no outbound access.

Please let me know if there is an additional configuration required to fully disable package installation on startup, or if this is an expected behavior.

If you want, I can also help tailor this to match the project’s issue template (e.g., adding steps to reproduce, expected vs. actual behavior).

Plugins

oh-my-opencode

OpenCode version

1.1.32

Steps to reproduce

Prepare an environment with restricted network access, allowing connectivity only to the LLM endpoint and no access to external package repositories.

Start the OpenCode container with the environment variable OPENCODE_DISABLE_AUTOUPDATE=1 set (for example, via docker run -e OPENCODE_DISABLE_AUTOUPDATE=1 ...).

Observe the container startup logs.

Notice that during startup, OpenCode attempts to install or update packages despite auto-update being disabled.

Screenshot and/or share link

No response

Operating System

macos and redhat linux

Terminal

Ghostty

Originally created by @suseemani on GitHub (Jan 24, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description I am attempting to start the container in a restricted environment that has access only to the LLM and no external network connectivity. To prevent automatic updates or package installations, I set the environment variable OPENCODE_DISABLE_AUTOUPDATE=1 when starting the container. However, during startup, OpenCode still attempts to install packages. This behavior makes it difficult to run the container in environments with limited or no outbound access. Please let me know if there is an additional configuration required to fully disable package installation on startup, or if this is an expected behavior. If you want, I can also help tailor this to match the project’s issue template (e.g., adding steps to reproduce, expected vs. actual behavior). ### Plugins oh-my-opencode ### OpenCode version 1.1.32 ### Steps to reproduce Prepare an environment with restricted network access, allowing connectivity only to the LLM endpoint and no access to external package repositories. Start the OpenCode container with the environment variable OPENCODE_DISABLE_AUTOUPDATE=1 set (for example, via docker run -e OPENCODE_DISABLE_AUTOUPDATE=1 ...). Observe the container startup logs. Notice that during startup, OpenCode attempts to install or update packages despite auto-update being disabled. ### Screenshot and/or share link _No response_ ### Operating System macos and redhat linux ### Terminal Ghostty
yindo added the bug label 2026-02-16 18:07:22 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 24, 2026):

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

  • #8729: Disable force dependency update while starting - Reports forced dependency reinstallation on every startup with bun add --force, causing 60-90+ second startup times
  • #6984: Config autoupdate only respected at global path - Reports that autoupdate: false config is ignored, causing unwanted auto-updates
  • #8830: Cannot use opencode in private network - Reports inability to use OpenCode in restricted network environments

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 24, 2026): This issue might be a duplicate of existing issues. Please check: - #8729: Disable force dependency update while starting - Reports forced dependency reinstallation on every startup with `bun add --force`, causing 60-90+ second startup times - #6984: Config autoupdate only respected at global path - Reports that `autoupdate: false` config is ignored, causing unwanted auto-updates - #8830: Cannot use opencode in private network - Reports inability to use OpenCode in restricted network environments Feel free to ignore if none of these address your specific case.
Author
Owner

@dhruvkej9 commented on GitHub (Jan 25, 2026):

OPENCODE_DISABLE_AUTOUPDATE should be boolean try with true

I have set it bashrc and it works fine for me (Ubuntu 24.04)

@dhruvkej9 commented on GitHub (Jan 25, 2026): OPENCODE_DISABLE_AUTOUPDATE should be boolean try with true I have set it bashrc and it works fine for me (Ubuntu 24.04)
Author
Owner

@suseemani commented on GitHub (Jan 25, 2026):

OPENCODE_DISABLE_AUTOUPDATE should be boolean try with true

I have set it bashrc and it works fine for me (Ubuntu 24.04)

Unfortunately, it is not working with docker container.

@suseemani commented on GitHub (Jan 25, 2026): > OPENCODE_DISABLE_AUTOUPDATE should be boolean try with true > > I have set it bashrc and it works fine for me (Ubuntu 24.04) Unfortunately, it is not working with docker container.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7500