On Wed, Mar 10, 2021 at 09:21:37AM -0800, Stephen Hemminger wrote: > There can be cases such as containers or other runtime environments > where DPDK may not be able to access the default runtime path. > This patch introduces DPDK_RUNTIME_DIR as an environment variable > to allow controlling and overriding the path. > > The example we have is DPDK application running in an untrusted > systemd container. In this case, it is not root, and XDG_RUNTIME_DIR > is not set (since it is not a user application), and /tmp is > blocked. The correct place for this application is to use /run. > > In any case, hard coded path assumptions are a problem. > > Signed-off-by: Stephen Hemminger <step...@networkplumber.org> > ---
Basic question, if the user/operator can set DPDK_RUNTIME_DIR in the container, can they not also set XDG_RUNTIME_DIR?
