macpijan
commented
5 years ago @pietrushnic I might have at some point in the past, but cannot say anything specific. Was it a one-time issue?
Open pietrushnic opened 5 years ago
macpijan
commented
5 years ago @pietrushnic I might have at some point in the past, but cannot say anything specific. Was it a one-time issue?
pietrushnic
commented
5 years ago @macpijan this thing happen when 2 containers are running. I just left first with ctrl-c and tried to run second. I'm not sure if we can protect ourselves against that.
macpijan
commented
5 years ago @pietrushnic This seems to happen when you interrupt the build (Ctrl+C) when running container in the noninteractive mode (without -i flag). In such a case, the container may still be running (see docker ps) and should be killed first. It did not happen before when the interactive mode was present. The interactive mode was disabled to allow build in CI (e.g. Jenkins). Running with the noninteractive mode is not so pleasant for local development. Maybe we should distinguish those 2 scenarios.
pietrushnic
commented
5 years ago @macpijan minimal solution is to let use know in Known issues section about this problem, other solution is to kill remaining containers before running next one. IMO secon option is ok since we expect to have only one container in system that do Yocto build.
fangxlmr
commented
5 years ago I encountered the same issue while using Yocto, but I have no clue on the reason behind and how to solve it.
pietrushnic
commented
5 years ago @fangxlmr temporary solution is simple, just list running containers and stop the one that is in background, then You can start again. IMO we should solve that in a robust way - we will get to that.
cdm0413
commented
3 years ago I just met the same issue, remove the bitbake.lock in the build path, and run again, it will works
Pallapu454
commented
3 years ago Hello, I am using Arago distribution, i tried to remove bitbake.lock, but i still get the same issue and again this bitbake.lock file is keep getting generated.
I have even restarted my PC also.
macpijan
commented
1 year ago @TomaszAIR Easy fix would be to keep the i flag when not running in CI.
Mohana493
commented
1 month ago Did you faced something like this?
NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection... NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection... NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection... NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection... NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection... NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection... NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection... NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection... ERROR: Unable to connect to bitbake server, or start one
How to fix it??
Mohana493
commented
1 month ago By removing bitbake .lock files also it's not executing
macpijan
commented
1 month ago We do not really use this repo anymore, please take a look at the description in the about section.
I wil lgo ahead and archive it
This repository is not currently used. For yocto projects we use https://github.com/siemens/kas container
Did you faced something like this?