-
Notifications
You must be signed in to change notification settings - Fork 562
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
Difficulty Setting Up Plugins for Auto-GPT in Docker on Arch Linux #235
Comments
It sounds like you've followed the necessary steps, but the plugins still aren't being recognized. Here is a suggestion might solve the issue:
volumes:
- ./plugins_config.yaml:/app/plugins_config.yaml:ro Make sure that the file path on the left correctly points to where your *. After making these changes, remember to restart Docker to ensure that the new volume bindings take effect: docker-compose down && docker-compose up -d If you continue to face issues, please check the application logs for any plugin-related error messages, as they can provide more insight into what might be going wrong. |
I am experiencing difficulty in setting up plugins for Auto-GPT when running it through Docker on my Arch Linux system. Despite following existing documentation and related issue threads, I haven't been successful in getting the plugins to work.
Environment
Steps to Reproduce
I read through the issue #185 on the Auto-GPT-Plugins repository but found that none of the resolutions there helped.
I attempted to integrate plugins with Auto-GPT using the following method:
Edited my docker-compose.yaml file as follows:
I extracted the contents of Auto-GPT-Plugins.zip into the ./plugins directory.
Created a plugins_config.yaml in the appropriate directory.
Expected Behavior
I expected that after setting up the plugins directory and the plugins_config.yaml, Auto-GPT would recognize and load the plugins upon startup.
Actual Behavior
The application does not seem to recognize or load the plugins_config.yaml. It behaves as if the plugin configuration file is not present.
Additional Context
The text was updated successfully, but these errors were encountered: