Run AutoGen Studio inside Docker container #2033
Replies: 1 comment
-
The solution was to rebuild the devcontainer. For rebuilding, I have used the VS code command palette "Dev Containers: Rebuild and Reopen in Container". This took around 50 minutes on my machine. Being inside the devcontainer, the command "autogenstudio ui" in a bash terminal launched the studio. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear community,
as recommended, I would like to run AutoGen Studio inside a docker container.
Previously, I was starting autogenstudio with the Batch command
autogenstudio ui
(as optional the port could be specified in the command). Afterwards, the UI was accessible in the web browser athttp://localhost:<portnumber>
and there was also a link to open localhost in the terminal output.To run inside a docker container I have tried
docker build -f studio/Dockerfile -t autogen_studio_img .
Dev Containers: Rebuild and Reopen in Container
I have not modified the offered
devcontainer.json
andDockerfile
files in.devcontainer\studio
.Now, I have the running dev container and an open Bash terminal. The previous Batch command for launching
autogenstudio ui
does not work in Bash. I thought autogenstudio might be running already, so I have tried to access the following ports in a browser tab with localhost:Port forwarding
but here the messageForbidden
gets returned in the browser tabForbidden
gets returned in the browser tabTrying to access the mentioned ports in the browser tab, always the following terminal output gets returned.
Where is my misunderstanding or what do I miss?
Has anybody accessed the autogenstudio ui, while running inside a Docker container?
Beta Was this translation helpful? Give feedback.
All reactions