Running in cloud from docker image BUG

[WNUMIK]

I have following error when running pnpm start in cloud in my docker container, my .env has CACHE_STORE=database but I also have URL for REDIS_URL What can be wrong?

 ["⛔ Error: Invalid cache store: database # Defaults to database. Other available cache store: redis and filesystem or required configuration missing."] 

 ["✓ Successfully connected to PostgreSQL database"] 

 ⛔ ERRORS
   Error starting agents: 
   {} 

also the second error I have is

# pnpm build

> eliza@ build /app
> turbo run build --filter=!eliza-docs

turbo 2.3.3

  x No package found with name 'eliza-docs' in workspace

 ELIFECYCLE  Command failed with exit code 1.
# 

[github-actions[bot]]

Hello @WNUMIK! Welcome to the elizaOS community. Thank you for opening your first issue; we appreciate your contribution. You are now an elizaOS contributor!

[Freytes]

What happens when you leave it blank?

[Freytes]

@WNUMIK there was a fix release in development can you try that?

[HashWarlock]

Run pnpm build-docker the docs aren't included in the docker image so this is the error you see

[WNUMIK]

I managed to run it but I have issue with env not sure why:

 ["⛔ Error: Telegram configuration validation failed:\nTELEGRAM_BOT_TOKEN: Required"] 

 ⛔ ERRORS
   Error starting agents: 
   {} 

I added .env to docker-compose-docs.yaml before building image, shouldn't it resolve .env issue? ofc I have TELEGRAM_BOT_TOKEN in .env so..

services:
    docs:
        build:
            dockerfile: Dockerfile.docs
            context: .
            target: serve
        ports:
            - "3000:3000"
        env_file:
            - .env

also this persists:

 ⛔ ERRORS
   Error starting agent for character Agent Bill the DeSci Guy: 
   {} 

 ["⛔ Error: Invalid cache store: database # Defaults to database. Other available cache store: redis and filesystem or required configuration missing."] 

 ⛔ ERRORS
   Error starting agents: 
   {} 

[WNUMIK]

I managed to run it but I have issue with env not sure why:

 ["⛔ Error: Telegram configuration validation failed:\nTELEGRAM_BOT_TOKEN: Required"] 

 ⛔ ERRORS
   Error starting agents: 
   {} 

I added .env to docker-compose-docs.yaml before building image, shouldn't it resolve .env issue? ofc I have TELEGRAM_BOT_TOKEN in .env so..

services:
    docs:
        build:
            dockerfile: Dockerfile.docs
            context: .
            target: serve
        ports:
            - "3000:3000"
        env_file:
            - .env

also this persists:

 ⛔ ERRORS
   Error starting agent for character Agent Bill the DeSci Guy: 
   {} 

 ["⛔ Error: Invalid cache store: database # Defaults to database. Other available cache store: redis and filesystem or required configuration missing."] 

 ⛔ ERRORS
   Error starting agents: 
   {} 

Same error with TELEGRAM_BOT_TOKEN: Required

for this config:

services:
    eliza:
        build:
            context: .
            dockerfile: Dockerfile
        stdin_open: true
        tty: true
        volumes:
            - /var/run/tappd.sock:/var/run/tappd.sock
            - eliza:/app/packages/client-twitter/src/tweetcache
            - eliza:/app/db.sqlite
        environment:
            - OPENAI_API_KEY=
            - CACHE_STORE=database
            - REDIS_URL=
            - POSTGRES_URL=
            - SERVER_PORT=3000
            - TELEGRAM_BOT_TOKEN=
            - COINMARKETCAP_API_KEY=
            - GIPHY_API_KEY=
            - COINGECKO_PRO_API_KEY=
            - COINGECKO_API_KEY=
            - AKASH_ENV=mainnet
            - AKASH_NET=https://raw.githubusercontent.com/ovrclk/net/master/mainnet
            - RPC_ENDPOINT=https://rpc.akashnet.net:443
            - AKASH_GAS_PRICES=0.025uakt
            - AKASH_GAS_ADJUSTMENT=1.5
            - AKASH_KEYRING_BACKEND=os
            - AKASH_FROM=default
            - AKASH_FEES=20000uakt
            - AKASH_DEPOSIT=500000uakt
            - AKASH_PRICING_API_URL=https://console-api.akash.network/v1/pricing
            - AKASH_DEFAULT_CPU=1000
            - AKASH_DEFAULT_MEMORY=1000000000
            - AKASH_DEFAULT_STORAGE=1000000000
            - AKASH_SDL=example.sdl.yml
            - AKASH_CLOSE_DEP=closeAll
            - AKASH_CLOSE_DSEQ=19729929
            - AKASH_PROVIDER_INFO=akash1ccktptfkvdc67msasmesuy5m7gpc76z75kukpz
            - AKASH_DEP_STATUS=dseq
            - AKASH_DEP_DSEQ=19729929
            - AKASH_GAS_OPERATION=close
            - AKASH_GAS_DSEQ=19729929
            - AKASH_MANIFEST_MODE=auto
            - AKASH_MANIFEST_VALIDATION_LEVEL=strict
        ports:
            - "3000:3000"
            - "5173:5173"
        restart: always

volumes:
    eliza:

[JoeyKhd]

@WNUMIK

I added .env to docker-compose-docs.yaml

Make sure you are using docker-compose.yaml and in the given example, - TELEGRAM_BOT_TOKEN= is empty. It seems you are mixing up the docs' Dockerfile with the normal one

[WNUMIK]

@WNUMIK

I added .env to docker-compose-docs.yaml

Make sure you are using docker-compose.yaml and in the given example, - TELEGRAM_BOT_TOKEN= is empty. It seems you are mixing up the docs' Dockerfile with the normal one

Can you describe how the process looks?

Here is mine. build using dockerfile, push to docker hub, pull on AWS from docker hub, create container, go in container pnpm install --no-frozen-lockfile pnpm build-docker pnpm start

I'm newbie to Docker so having hard time with it right now

[TbLtzk]

I also have the error saying No package found with name 'eliza-docs' I do not want to spam this issue. Should I open a separate issue for that? For now, I solved the problem by removing the --filter=!eliza-docs param from the turbo build command.

[WNUMIK]

I also have the error saying No package found with name 'eliza-docs' I do not want to spam this issue. Should I open a separate issue for that? For now, I solved the problem by removing the --filter=!eliza-docs param from the turbo build command.

use pnpm build-docker

[TbLtzk]

nvm, I was operating on an old fork of this repo. I still have issues with building via docker, but for now, I try to resolve them on my own. Sorry for bothering you

[TbLtzk]

solved it on my local machine. I'm on a windows OS and it was a matter of line endings. Running git config --local core.autocrlf false keeps the LF ending from the repo. After that, the docker-compose build went smoothly to the end.

[WNUMIK]

compose

you did a deploy to AWS?

cause this is the place where I have troubles

[WNUMIK]

nvm im dumb