Fabian Kramm

@masterful thanks for your input! We decided to turn the `.env` loading default off as its causing a lot of confusion for people. In v6 you can use the following...

@oleksandr-vynnyk thanks for creating this issue! Could you provide the complete log output of DevSpace when this issue occurs? Does the node where the pod is running on have disk...

@oleksandr-vynnyk thanks for the information! Does this also happen if you exclude some of the folders via `excludePaths`? Are you running on arm architecture?

@oleksandr-vynnyk I see, I think the problem here is actually not the space on the device and [rather the amount of inotify watches that is allowed](https://askubuntu.com/questions/1088272/inotify-add-watch-failed-no-space-left-on-device), you can check this...

@artushin the problem was the underlying [notify library](https://github.com/rjeczalik/notify) we were using that was not supporting this. We just released DevSpace version v5.14.4 where this should be fixed and which should...

@noizwaves thanks for creating this issue! I'm still a little bit confused what could cause this issue to be honest, but after some digging this seems to me golang related...

@noizwaves we are still investigating this issue, but it seems like binaries that were natively compiled on an M1 mac work fine and it seems to be an issue with...

@noizwaves @evyros @uncvrd Good news, we actually found the underlying problem and we can fix it. We also know why it works compiling DevSpace locally, but not with the released...

@antonlisovenko thanks for creating this issue! Yes, I think we could add a json schema

@SohumB thanks for creating this issue! Yes this seems like a bug, we'll fix this for the next release!