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
It seems that, when starting a container via runsc run from an OCI specification file, sysctl options in the specification file won't take effect inside the container.
Steps to reproduce
Make a rootfs directory and unpack a debian-slim image into it: mkdir bundle && cd bundle && mkdir --mode=0755 rootfs docker export $(docker create debian:bullseye-slim) | sudo tar -xf - -C rootfs --same-owner --same-permissions
Create a simple script in rootfs to dump a sysctl setting:
Description
It seems that, when starting a container via
runsc run
from an OCI specification file, sysctl options in the specification file won't take effect inside the container.Steps to reproduce
Make a rootfs directory and unpack a debian-slim image into it:
mkdir bundle && cd bundle && mkdir --mode=0755 rootfs
docker export $(docker create debian:bullseye-slim) | sudo tar -xf - -C rootfs --same-owner --same-permissions
Create a simple script in rootfs to dump a sysctl setting:
Generate a config.json:
runsc spec -- /test_script
Add the following to the
"linux"
block of the config:Then
sudo runsc run test_script
will show a value of 7200, not 1000.runsc version
docker version (if using docker)
No response
uname
Linux 5.15.0-101.103.2.1.el9uek.x86_64 #2 SMP Tue May 2 01:10:45 PDT 2023 x86_64 x86_64 x86_64 GNU/Linux
kubectl (if using Kubernetes)
No response
repo state (if built from source)
No response
runsc debug logs (if available)
No response
The text was updated successfully, but these errors were encountered: