Fabian Kramm

@lukasmrtvy thanks for creating this issue! Yes thats a good idea, we should add support for patches with kustomize

@ruckc thanks for reporting this! Seems like apparmor might be a problem somehow. As suggested [here](https://github.com/docker/for-linux/issues/1199), applying `apparmor=1 lsm=lockdown,yama,apparmor,bpf` as kernel parameters has helped for them.

@aliusmiles thanks for creating this issue! Currently the problem with profile activation from variables is that you can use profiles to change variable default values for example, so the order...

@aliusmiles thats correct, predefined variables cannot be overriden and would work, however all other variables wouldn't. We can maybe implement something that the variables that are used for activation are...

@aliusmiles that is true, however one use case which would be very useful as well would be variables from commands, where you essentially could define your custom logic when a...

@mnpenner thanks for creating this issue! Yes seems like that shouldn't happen, we'll investigate and release a fix for this as soon as possible. Regarding the `devspace sync` issue: DevSpace...

@nevalla thanks a lot for creating this issue! Yes you are correct, seems like this is a bug

@nachin yes the correct answer for the current version is: ```yaml commands: - name: echo-test command: run() { devspace enter --container test-container -- sh -c "echo $1"; }; run ```...

@arcanis thanks for creating this issue! Yes the http is currently hardcoded, but we can easily make that dynamic, thanks for pointing that out!

@arcanis we just released v5.15.0-beta.0, would be great if you could confirm that this fixes your problem