Error when running wmill sync pull due to temp dir?
I'm trying to run
wmill sync pull
for the first time (on a macbook) and it's immediately throwing this error:
The path changes each time, but doesn't seem to be using any of the common environment variables like TMPDIR. Is there a setting to change where the wmill cli
stores temporary files?26 Replies
I just realized that error is coming from the server, not the client. But I still have the same issue, it keeps trying to use /usr/src/app instead of TMPDIR
The error is coming from the client
That error was from the wmill cli, but I see it in the windmill server logs too:
I'm a bit confused by that actually
I'm running the windmill server container as a non-root user. I just checked the example docker-compose file and it doesn't look like it specifies a user, but /usr/src/app is owned by root
Is it expected to run as root? Or it might be a bug if it's just only been tested that way
I set the work_dir to /tmp for the windmill server container and that made the error go away
👍
How are you running things btw ?
What is this work_dir setting?
Sorry, it's
working_dir
for docker-compose.yml. I'm using hashicorp nomad to run it though, and that one is work_dir
for the same option. I think you can specify it in the Dockerfile too, but I still think it might be a bug if the app doesn't honor the TMPDIR variable
https://github.com/compose-spec/compose-spec/blob/master/spec.md#working_diri have exactly the same problem. i'm using the original
docker-compose.yml
file: https://github.com/windmill-labs/windmill/blob/main/docker-compose.yml
client:
I will look into it, we did changes yesterday about it
server:
ty appreciated
if i open the url directly i get the same error btw:
http://my-windmill-instance/api/w/flickvibe/workspaces/tarball?archive_type=zip&plain_secret=false&skip_variables=false&skip_resources=false&skip_secrets=false&include_schedules=false
should be fixed on next commit
wow, that was fast
so whenever there is a new version in https://github.com/windmill-labs/windmill/releases i can update my docker image?
it doesn ot require a release
should be ready in a few mins
i stopped docker compose, ran docker compose pull and saw it refetched the "lsp" image
restarted the services, but still got the same error when i try to sync. maybe i'm too impatient 😅
you can repull now
it pulled the worker_native image and now the sync works!
impressive, thx a lot
not sure if this is related, but pushing doesn't work for me
error on the client:
well is that true ? Does the file not exist ?
it does not exist locally, yes
well then ...
i pulled from the server, changed two files without deleting any and the pushed again. not sure why they should not be there
Are you 100% sure you didn't delete or rename the file ?
i'll double check if i accidentally deleted them. but pulling again does not restore any files
Delete the flow folder and pull again instead
still no flow.yaml file. i checked my local history, not even with the very first pull there was a yaml file. also not a json file.
maybe a bug with the --json flag?
i'm using
wmill sync pull --json
and wmill sync push --json
yes looks like a bug with the --json flag indeed
can reproduce with --json but noy --yaml
yep, can confirm it works without the flag