Skip to content

Extension fails to start: executable file not found in $PATH #11035

Answered by smira
mottetm asked this question in Q&A
Discussion options

You must be logged in to vote

Converted this into a discussions, as it's a question.

This error usually means that a shared library required by the executable is missing in the container.

Extensions solve it one of several ways:

  • static builds
  • include library into the image
  • if it's e.g. musl libc, mount it up from Talos host

Either way is fine.

The error can be easily reproduced by copying out the extensions service rootfs as a separate container image and doing docker run on it.

Replies: 2 comments 6 replies

Comment options

You must be logged in to vote
0 replies
Answer selected by mottetm
Comment options

You must be logged in to vote
6 replies
@mottetm
Comment options

@frezbo
Comment options

@smira
Comment options

@mottetm
Comment options

@mottetm
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants
Converted from issue

This discussion was converted from issue #11034 on May 16, 2025 13:54.