Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tarantool/tarantool 3.0.1 image is not convenient to use in ci due to TT_INSTANCE_NAME and TT_APP env variables #9993

Open
ochaton opened this issue May 6, 2024 · 0 comments

Comments

@ochaton
Copy link
Member

ochaton commented May 6, 2024

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant