gitmonster

Hi @anna-geller , thanks. I used the latest version with same results. Then I tried 0.16.1, then the dev-snapshot, every time with the same issue. Btw. I use docker-desktop with...

Sorry, but starting kestra without custom docker-compose config and ``` docker run --pull=always --rm -it -p 28080:8080 --user=root -v /var/run/docker.sock:/var/run/docker.sock -v /tmp:/tmp kestra/kestra:latest-full server local ``` and using the test...

I tried again and removed the /tmp mount completely, thinking it was a permissions issue. Without success. Now I'm going to deploy Kestra in a live environment and see if...

@paulgrainger85 I think it's not WSL related since I deployed with the above settings in our companys docker infra and had the same issues. All works well but script flows.

Hey @tchiotludo, yes it's - linux based on ubuntu-server:20.04 - swarm environment - deployed with docker compose - kestra version is pinned to 0.16.1 here is the config ``` services:...

yes, but as you can see, all kestra related deployment is constrained to a single host.

No, It's not windows-only related. As you can see I started out on ubuntu:20.04/windows/WSL2 then deployed to a pure linux environment. This is working: 

yes. 

@loicmathieu I tried with `/tmp/kestra-wd:/tmp/kestra-wd` settings yesterday but couldn't deploy the entire service cause the /tmp/kestra-wd folder could not be created on the host. Now I redeployed with `/tmp/kestra-wd:/tmp/kestra-wd` successfully...

with /tmp/kestra-wd existing on the host: