You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am deploying binary files directly to OpenWrt on an embedded device, and I have no plans to use Docker, as deploying the binaries directly fully meets the performance requirements. OpenWrt's procd (similar to systemd) does not support setting the working directory, although it allows setting environment variables. However, the program still generates some files that are not controlled by the environment variables. Since OpenWrt's procd cannot provide the current working directory to the program (as it doesn't exist), I am wondering if the program offers a parameter or environment variable to manually specify the working directory.
The text was updated successfully, but these errors were encountered:
I am deploying binary files directly to OpenWrt on an embedded device, and I have no plans to use Docker, as deploying the binaries directly fully meets the performance requirements. OpenWrt's procd (similar to systemd) does not support setting the working directory, although it allows setting environment variables. However, the program still generates some files that are not controlled by the environment variables. Since OpenWrt's procd cannot provide the current working directory to the program (as it doesn't exist), I am wondering if the program offers a parameter or environment variable to manually specify the working directory.
The text was updated successfully, but these errors were encountered: