-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Bot Doesn't Respond to Tagged Tweets When Running in Docker #1372
Comments
Can you provide logs from your docker container ? |
Hello here Here some tips 1. Comprehensive Summary of the IssueThe bot fails to respond to tagged tweets when running in a Docker container, despite functioning correctly when executed directly with 2. Root Cause of the ProblemThe root cause is the incorrect or missing configuration of the 3. Step-by-Step Solution
|
@vanshika-srivastava logs were normal as nothing happened, I will test and get back to you guys ASAP |
@usama-saeed831 yes please try our latest version and report me back. |
When I run the bot using
npm start
, everything works perfectly: it tweets and responds to tagged tweets as expected. However, when I run the bot inside Docker, I encounter the following issues:Environment Variable: The
OPENAI_API_KEY
is required when running the bot in Docker (docker compose up
) , but it's not needed when running it directly (without Docker).Tweeting: The bot tweets without any issues when running in Docker.
Response to Tagged Tweets: The problem arises when the bot is supposed to respond to tweets it's tagged in. While it tweets fine, it doesn't respond to any tagged tweets.
I’ve checked the logs, and everything seems normal—there are no visible errors.
Could anyone help identify what might be causing this issue when running the bot inside Docker?
The text was updated successfully, but these errors were encountered: