Issue Running a Local Development Environment with Rootless Docker

Hey Dev Team,

I am following the instructions on https://docs.optimism.io/stack/dev-node .

I am trying to run my optimism node on a remote server, which I have not been given root access. To accomplish this I have had to clone to kurtosis github repo and build the binary on my machine, replacing every instance of "/var/run/docker.sock:/var/run/docker.sock" to my rootless docker.sock located at export DOCKER_HOST=unix://$XDG_RUNTIME_DIR/docker.sock, while also setting up that DOCKER_HOST variable.

Quoting their contributing docs-> "Once the project has built, run ./cli/cli/scripts/launch-cli.sh as if it was the kurtosis command"

I am using that command to run, once I have set up a directory with the specified network-config.yaml as specified in the link.

./kurtosis/cli/cli/scripts/launch-cli.sh run github.com/ethpandaops/optimism-package --args-file ./network-config.yaml

This correctly starts a kurtosis engine and runs but then has the output:

As you can see only two UUIDs are running compared to the 7 on the linked guide.

Although running docker ps gives me this output:

So I still tried to run the cast send command to interact with the environment. I am having difficulties there as well.

With this command:

cast send --mnemonic 'test test test test test test test test test test test junk' --mnemonic-path "m/44'/60'/0'/0/0" \
    --to "<standard bridge address>" --amount "<amount in ETH>eth" --rpc-url "http://127.0.0.1:<rpc port of el-1-geth-lighthouse service>"

I cannot seem to find my standard bridge address, you specified that it should be in the output from doing the kurtosis run but I do not seem to see it.

Also --mnemonic-path and --to are not flags according to the docs for cast send on foundry. https://book.getfoundry.sh/reference/cast/cast-send

Was wondering if I could get clarification on all of this. Trying to run some benchmarks on optimism on a cloud server.

Start with the dev-node documentation, the referenced network-config.yaml, and cli/cli/scripts/launch-cli.sh; reproduce the shown command with rootless Docker and inspect its output. Done means the documentation clearly explains rootless Docker setup, expected services and bridge-address output, and uses valid cast send flags.