Ah, interesting. It tries to create the file in the working directory of the generic-worker process. It looks like Worker Runner doesn't explicitly set a working directory for generic-worker, so it should inherit the working directory of the start-worker process. In the systemd configuration [here](https://github.com/mozilla-platform-ops/monopacker/blob/main/scripts/worker-runner-gw-systemd/20-add-and-enable-systemd-service.sh#L18-L25) I don't see an explicit Working Directory (see https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html#WorkingDirectory= to see how to set one). That probably should be set to a writable path for the user that runs generic-worker.
Bug 1859323 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Ah, interesting. It tries to create the file in the working directory of the generic-worker process. It looks like Worker Runner doesn't explicitly set a working directory for generic-worker, so it should inherit the working directory of the start-worker process. In the systemd configuration [here](https://github.com/mozilla-platform-ops/monopacker/blob/118673ca767614bfade3c8e58645f0a6a652ed72/scripts/worker-runner-gw-systemd/20-add-and-enable-systemd-service.sh#L18-L25) I don't see an explicit [`WorkingDirectory`](https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html#WorkingDirectory=) setting. That probably should be set to a writable path for the user that runs generic-worker.
Ah, interesting. It tries to create the file in the working directory of the generic-worker process. It looks like Worker Runner doesn't explicitly set a working directory for generic-worker, so it should inherit the working directory of the start-worker process. In the [systemd configuration](https://github.com/mozilla-platform-ops/monopacker/blob/118673ca767614bfade3c8e58645f0a6a652ed72/scripts/worker-runner-gw-systemd/20-add-and-enable-systemd-service.sh#L18-L25) I don't see an explicit [`WorkingDirectory`](https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html#WorkingDirectory=) setting. That probably should be set to a writable path for the user that runs generic-worker.
Ah, interesting. It tries to create the file in the working directory of the generic-worker process. It looks like Worker Runner doesn't explicitly set a working directory for generic-worker, so it should inherit the working directory of the start-worker process. In the systemd [Service configuration](https://github.com/mozilla-platform-ops/monopacker/blob/118673ca767614bfade3c8e58645f0a6a652ed72/scripts/worker-runner-gw-systemd/20-add-and-enable-systemd-service.sh#L18-L25) I don't see an explicit [`WorkingDirectory`](https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html#WorkingDirectory=) setting. That probably should be set to a writable path for the user that runs generic-worker.
Ah, interesting. It tries to create the file in the working directory of the generic-worker process. It looks like Worker Runner doesn't explicitly set a working directory for generic-worker, so it should inherit the working directory of the start-worker process. In the systemd [Service](https://github.com/mozilla-platform-ops/monopacker/blob/118673ca767614bfade3c8e58645f0a6a652ed72/scripts/worker-runner-gw-systemd/20-add-and-enable-systemd-service.sh#L18-L25) configuration I don't see an explicit [`WorkingDirectory`](https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html#WorkingDirectory=) setting. That probably should be set to a writable path for the user that runs generic-worker.