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
Yes. It is expected. Only the process forked from the first process of the container will have its environment variables. The nsenter has the same behavior.
Please try env "$(xargs -0 -L1 -a /proc/46983/environ)" nsexec -m /proc/46983/ns/mnt -p /proc/46983/ns/pid sh -c "export" . I'm not sure whether it will work perfectly 🤔
When I execute the below command
nsexec -m /proc/46983/ns/mnt -p /proc/46983/ns/pid sh -c "export"
It shows not the environment variables inside the container, but the local environment variables.
The text was updated successfully, but these errors were encountered: