metagpt.config.NotConfiguredException: Set OPENAI_API_KEY first about metagpt HOT 6 CLOSED

@voidking

from metagpt.

@gnoejuan
I'm sorry I couldn't locate the problem according to your description.
I have a few suggestions that might help:

1. Make sure your workdir in container is /app/metagpt which contains the MetaGPT codes, and exec python startup.py "something" in the /app/metagpt directory.
2. Make sure the config directory is in workdir. The correct path like this: /app/metagpt/config/key.yaml. Then the program can find the config.
3. Change the config content by mounting a file or sed in Dockerfile. Make sure the program can work by configfile.
4. Give parameters through environment variables.

By the way, you can debug your container by the following step:

docker run --name test -d docker.io/library/metagpt:latest tail -f /dev/null
docker exec -it test /bin/sh
cat config/key.yaml
python startup.py "do something"
export OPENAI_API_KEY="xxx"
python startup.py "do something"
...

Then you can find where the problem is.

from metagpt.

Awesome! Thank you!

So, looks like with the command line I was running earlier, the mount was in the wrong place! Good catch!

But, before I figured out the mount issue, when I was testing the

export OPENAI_API_KEY="xxx"
python startup.py "do something"

step, I ran into the NotConfiguredException.

So, I'm happy and taken care of ( I can modify the Job to use the config ), the documentation in the Readme does suggest that an environment variable should also be a viable approach.

from metagpt.

I know the problem, because config.yaml has higher priority, so the stub in config.yaml blocks the env variable. I will fix this in the next update

from metagpt.

da11d38
pushed. check it again.

from metagpt.

Yup! That worked! The Job was able to complete using the environment variables!

from metagpt.