⚙️Autogen version 0.2.0 includes a breaking change where code execution now happens inside a Docker container by default.
🛠️If you upgrade to Autogen 0.2.0 without updating your code, it may not work properly.
🐳Understanding how to use Docker is crucial for running upgraded code in Autogen 0.2.0.
💻If you don't want to use Docker, you can set the 'use Docker' property to false in the user proxy agent.
🔧To upgrade to Autogen 0.2.0, use the command 'pip install -U autogen' in your terminal.
What is the breaking change in Autogen 0.2.0?
—The breaking change in Autogen 0.2.0 is that code execution now happens inside a Docker container by default.
What should I do if my code breaks after upgrading to Autogen 0.2.0?
—If your code breaks after upgrading to Autogen 0.2.0, you should update your code to run properly inside a Docker container or set the 'use Docker' property to false in the user proxy agent.
Do I have to use Docker in Autogen 0.2.0?
—No, using Docker is not mandatory in Autogen 0.2.0. You can set the 'use Docker' property to false in the user proxy agent and run your code locally.
How do I upgrade to Autogen 0.2.0?
—To upgrade to Autogen 0.2.0, use the command 'pip install -U autogen' in your terminal.
Where can I find more information about Autogen 0.2.0?
—You can find more information about Autogen 0.2.0 by watching the video above or visiting the Autogen GitHub repository.
00:00Autogen version 0.2.0 introduces a breaking change - now code execution happens inside a Docker container by default.
00:42To use Autogen 0.2.0 without Docker, set the 'use Docker' property to false in the user proxy agent.
02:19To upgrade to Autogen 0.2.0, use the command 'pip install -U autogen' in your terminal.
04:01If your code breaks after upgrading to Autogen 0.2.0, update your code to run properly inside a Docker container.
06:01Using Docker is not mandatory in Autogen 0.2.0 - you can run your code locally without Docker.
