I experience a strange error.
Basically a normal starting-app. minor modifications, but no removed files or similar. Even tried the same with a completely blank app. Same error.
Trying to app.run ends up with the error.
I run on Windows, but in a dev-container based on debian.
I own a Homey Pro and have it standing next to me. Its in the same network, what doesnt seem to matter too much.
ok, thats totally fine. what is not totally fine is, that they do not check what kind of app your trying to run, and alerting you about it or even automatically switch … i need a homey anyways.
You can still use Docker to develop Homey Pro apps, I just find that using the Docker setup is of limited use and I don’t really like having to run Docker continuously just for Homey app development.
The error that you get seems to be related to the Docker container, that’s why I suggested using --remote as a workaround. I noticed you posted an issue on the SDK Github repo about it, let’s hope it gets picked up.
it seems hard to actually find the code for that error i have seen, or else i would have investigated myself and tried to fix it.
is the code for the ecosystem closed source or something, or where can i find this homey apprunner lib?
the docker setup seems a lot faster than the homey remote installation and debugging. it takes quite some time to build and deploy
Short update…as suggested by @robertklep it seems it’s a race condition. If files are stored on a slower network drive, they are not upload fast enougt to the Docker container.
Running the same repository on a local SSD drive solved this issue.
commented on github as well. i dont believe its a speed issue. but rather an issue of where the files are stored and how docker can access them or not.