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

Agent is stuck on start (Docker/Cloud) v0.25.6-alpha.1 #3385

Open
WNUMIK opened this issue Feb 8, 2025 · 1 comment
Open

Agent is stuck on start (Docker/Cloud) v0.25.6-alpha.1 #3385

WNUMIK opened this issue Feb 8, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@WNUMIK
Copy link

WNUMIK commented Feb 8, 2025

Describe the bug

Bug on start of agent (v0.25.6-alpha.1) in cloud using docker, start of agent is stuck on very beginning not outputting any errors and also not continuing with start. (Agent is not responding)

To Reproduce

  1. Create docker-compose of newest version of Eliza v0.25.6-alpha.1
  2. Upload to cloud and start docker-compose

Expected behavior

Agent starts and functions normally as on local and as older versions.

Screenshots

Image

Additional context

I built docker-compose for linux amd64, also did this for older versions and everything was working fine.

Plugins I use for my Agent:
plugins: [AwsS3Service, TranscriptionService, BrowserService, bootstrapPlugin, PdfService, dexScreenerPlugin, ImageDescriptionService, SpeechService, webSearchPlugin, twitterPlugin, giphyPlugin, coingeckoPlugin],

Clients and model I use for my Agent:

clients: [Clients.TELEGRAM, Clients.TWITTER],
modelProvider: ModelProviderName.OPENAI,

It is working on local/desktop.

@WNUMIK WNUMIK added the bug Something isn't working label Feb 8, 2025
@WNUMIK WNUMIK changed the title Agent is stuck on start (Docker/Cloud) Agent is stuck on start (Docker/Cloud) v0.25.6-alpha.1 Feb 8, 2025
@alois8
Copy link

alois8 commented Feb 12, 2025

I had the same issue.
I resolved it by uncommenting tty: true in docker-compose.yaml, which made the startup more verbose.
This helped me identify the root cause — a mistake in the character.json file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants