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
I use lots of docker images of tarantool/tarantool in CI and github workflows to test libraries with tarantool/luacheck, tarantool/luatest, luacov and so on. They all are installed during CI jobs and have /usr/bin/env tarantool as executable.
Since 3.0.0 when environment variables TT_INSTANCE_NAME and/or (don't know exactly) TT_APP are set, tarantool jumps into DB, and that is not OK.
Now I use this hack, to wipe out TT_* environment variables from docker images, maybe you could suggest something better?
for f in $(env | grep TT | while read -r line; do cut -f1 -d'=' ; done); do unset $f; done
The text was updated successfully, but these errors were encountered:
I use lots of docker images of tarantool/tarantool in CI and github workflows to test libraries with tarantool/luacheck, tarantool/luatest, luacov and so on. They all are installed during CI jobs and have
/usr/bin/env tarantool
as executable.Since 3.0.0 when environment variables TT_INSTANCE_NAME and/or (don't know exactly) TT_APP are set, tarantool jumps into DB, and that is not OK.
Now I use this hack, to wipe out TT_* environment variables from docker images, maybe you could suggest something better?
The text was updated successfully, but these errors were encountered: