-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: fvm switch fails on some systems with running local cluster #3765
Labels
bug
Something isn't working
help wanted
Good issue for community involvement
no-stale
Opt-out of closing issue due to no activity
Comments
Dockerfile for refernce:
|
Stale issue message |
For linux, probably need to see https://stackoverflow.com/questions/16764946/what-generates-the-text-file-busy-message-in-unix |
digikata
changed the title
[Bug]: fvm switch fails in a docker container with running local cluster
[Bug]: fvm switch fails on some systems with running local cluster
Feb 16, 2024
Fix tested and worked on Linux and within a linux docker env. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
help wanted
Good issue for community involvement
no-stale
Opt-out of closing issue due to no activity
What happened
fvm switch
in a docker container failed with "Error: Text file busy (os error 26)"Expected behavior
fvm switch
orfvm update
successfully switches versionsDescribe the setup
Running fluvio and fvm switch on some os environments with a running cluster can lead to this error.
How to reproduce it (as minimally and precisely as possible)
fvm install latest
fluvio cluster start
Starts a local clusterfvm switch stable
Causes an "Error: Text file busy (os error 26)"
Additional context
A workaround is to shut down the local fluvio cluster, switch versions, then restart. On switch for linux environments, the binaries may need to be unlinked before copying new binaries of the switch-to version.
An intermediate fix is to detect running instances and ask them to shutdown, but this is likely more complex than doing an unlnk.
The text was updated successfully, but these errors were encountered: