Make test containers compatible with our CI environment

--net=none is super counterintuitive here, I know. But it works: nested
containers do not try to setup their own networking and thus avoid:

  * Error: netavark: Sysctl error: IO Error: Read-only file system (os error 30)
  * Caused by attempting to write into /proc/sys/net/ipv4/ip_forward which
    is not writable due to our CI runner already being a container

Container still inherits runner networking setup which makes this
effectively equal to --net=host but in a roundabout way.

Signed-off-by: Vitaliy Potyarkin <v.potyarkin@yadro.com>
This commit is contained in:
Vitaliy Potyarkin 2025-01-14 18:05:22 +03:00
parent 10fdf60eaa
commit fbeeed8eae

View file

@ -53,8 +53,8 @@ jobs:
printf "[TestFrostFS]\ntype = frostfs\nendpoint = localhost:8080\nwallet = /config/wallet.json\nplacement_policy = REP 1\nrequest_timeout = 20s\nconnection_timeout = 21s" > /config/rclone.conf
echo "run frostfs aio container"
docker run -d --name aio $AIO_IMAGE:$AIO_VERSION --restart always -p 8080:8080
docker run -d --net=none --name aio $AIO_IMAGE:$AIO_VERSION --restart always -p 8080:8080
echo "issue creds"
docker exec aio /usr/bin/issue-creds.sh native
echo "copy wallet"