#I've never seen this error message. Was

1 messages · Page 1 of 1 (latest)

restive sparrow
restive sparrow
#

was working on getting docker going in docs recorder...working, but surprised

#

cc @granite zephyr

granite zephyr
#

maybe because the recorder module does all its tasks twice, so the container from the first round is still running?

#

try it without the --name

restive sparrow
#

yep. will try without.

#

was trying a diff name first

#

but I see what you mean

granite zephyr
#

or add a docker stop my-mariadb at the end

#

since it has --rm already that should remove it and clear the ground for the next run

restive sparrow
#
dagger call exec --cmd "docker run --rm --detach -p 3306:3306 --env MARIADB_ROOT_PASSWORD=secret mariadb:10.11.2" \
exec --cmd "docker ps | grep mariadb" \
gif -o cast3.gif
#

ah, port already taken too

granite zephyr
#

ah ok, so then i guess you have to explicitly stop it

#

or have the mariadb service already running, in this case the screen recording will start with the docker ps step, which is also fine

restive sparrow
#

if I run this twice locally...no name, no ports

docker run --rm --detach --env MARIADB_ROOT_PASSWORD=secret mariadb:10.11.2

I end up with two containers

#

But if I run the same with recorder, I only get one...

#

so I don't undertand the "runs twice thing"

granite zephyr
#

I saw this in the PR All commands are run twice: a first time to warm up the dagger cache; a second time in the recording.

restive sparrow
#

ah, so really only works for idempotent execs

#

unless we have option to not run the first cache-warming step for some execs

#

this time I caught both

#

also seeing some cached things end up in there