Hi,
I will be documenting my journey into testground. I plan to write tests in rust lang for my app.
First step was to install docker, I did but in rootless mode (more on that later) then I installed go.
Worked fine until I tried testground daemon the command was not recognised. I asked on discord and @Jorropo helped me.
When installing go they don’t tell you to add a PATH to .bashrc
export PATH="$HOME/go/bin:$PATH"
Easy fix!
Next step was to run a test plan.
Can’t connect to docker. Docker host endpoint is wrong. Oh no!
Being not super familiar with docker I thought re-intalling docker without the rootless mode would work but it didn’t. You need rootless mode to use the docker extension in VScode anyway.
Back to .bashrc!
export DOCKER_HOST=unix:///run/user/1000/docker.sock
Did the trick since it wasn’t the default.
I was finally able to run the example but some containers errored.
Jan 10 22:14:28.645340 INFO container isn't running; starting {"container_name": "testground-redis"}
Jan 10 22:14:29.149892 ERROR starting container failed {"container_name": "testground-redis", "container_name": "testground-redis", "error": "Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: write sysctl key net.core.somaxconn: open /proc/sys/net/core/somaxconn: no such file or directory: unknown"}
Jan 10 22:14:29.153360 INFO container isn't running; starting {"container_name": "testground-sync-service"}
Jan 10 22:14:29.656777 ERROR starting container failed {"container_name": "testground-sync-service", "container_name": "testground-sync-service", "error": "Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: write sysctl key net.core.somaxconn: open /proc/sys/net/core/somaxconn: no such file or directory: unknown"}
Jan 10 22:14:29.659622 INFO container isn't running; starting {"container_name": "testground-influxdb"}
Jan 10 22:14:30.002163 INFO container isn't running; starting {"container_name": "testground-sidecar"}
Jan 10 22:14:30.387401 ERROR starting container failed {"container_name": "testground-sidecar", "container_name": "testground-sidecar", "error": "Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting \"proc\" to rootfs at \"/proc\" caused: mount through procfd: operation not permitted: unknown"}
Jan 10 22:14:30.387479 ERROR doRun returned err {"err": "healthcheck fixes failed; aborting:\nChecks:\n- local-outputs-dir: ok; directory exists.\n- control-network: ok; network exists.\n- local-grafana: failed; container state: exited\n- local-redis: failed; container state: created\n- local-sync-service: failed; container state: created\n- local-influxdb: failed; container state: exited\n- sidecar-container: failed; container state: created\nFixes:\n- local-outputs-dir: unnecessary; \n- control-network: unnecessary; \n- local-grafana: ok; container created.\n- local-redis: failed; failed to start container.\n- local-sync-service: failed; failed to start container.\n- local-influxdb: ok; container created.\n- sidecar-container: failed; failed to start container.\n"}
I’ll see tomorrow, if I start writing my own test plans or if I try to fix this mess.
). Works fine, 80mb is manageable.
(in most languages / things that doesn’t use after link time relocations)
