You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
kas-container is very useful for CI, but it's useful as well for a local environment where you want to build in a Linux OS that is incompatible with Yocto.
When building locally with kas-container I see the NOTE: Unable to use interactive mode for this terminal, using fallback message from Bitbake. I understand this is the default way for the CI environment, but it would be nice to change it with some option when using kas-container from your PC.
My guess is it has to do with how the container is used. I was thinking like passing down the -i flag, like kas-container --runtime-args '-i' build but that doesn't work
The text was updated successfully, but these errors were encountered:
Hi @jetm , if you start the kas container from a terminal you should get an interactive terminal (showing the bitbake progress bars). If you run kas-container shell, you even get a fully interactive shell to do things in the yocto environment.
I have the same setup as you but I don't get the warning about a non-interactive terminal. Which terminal emulator are you using and (perhaps more interestingly), how did you install it? What's the value of your TERM env variable?
I installed kas from AUR package. Locally, I modified the PKGBUILD to install kas 4.7.
Terminal: kitty 0.39.1 created by Kovid Goyal
TERM: xterm-kitty
jetm
changed the title
Is it possible to add an interactive mode to kas-interactive and see the building logs as normally Bitbake shows?
Is it possible to add an interactive mode to kas-container and see the building logs as normally Bitbake shows?
Feb 6, 2025
Hi,
kas-container
is very useful for CI, but it's useful as well for a local environment where you want to build in a Linux OS that is incompatible with Yocto.When building locally with
kas-container
I see theNOTE: Unable to use interactive mode for this terminal, using fallback
message from Bitbake. I understand this is the default way for the CI environment, but it would be nice to change it with some option when using kas-container from your PC.My guess is it has to do with how the container is used. I was thinking like passing down the
-i
flag, likekas-container --runtime-args '-i' build
but that doesn't workThe text was updated successfully, but these errors were encountered: