-
Notifications
You must be signed in to change notification settings - Fork 6.6k
Dockerfile for AutoGen Studio fails to build due to UID conflict #5929
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
Comments
Thanks @gunt3001, Do you want to push a fix? I can help merge that in. |
Sure thing, I can create a PR. I'm going to make the assumption that we want to keep using the base image from Microsoft's registry. I update so that re-use existing |
we can just revert to standard
|
P.S Some thing like ..
|
Yep, thanks! I managed to build the image with the fixed Dockerfile and Studio was indeed complaining about that. I created the PR. I'm also adding an additional commit updating some parts of the docs that refer to this Dockerfile to be consistent. |
Thanks. PR is looking good. P.S .. are you hosting AGS in a multi user env or mostly just local testing? |
Currently only local testing :) |
What happened?
Describe the bug
The Dockerfile for Autogen Studio at python/packages/autogen-studio/Dockerfile fails to build.
The issue occurs at the step that adds a user with UID 1000 (
RUN useradd -m -u 1000 user
). Since the base image (mcr.microsoft.com/devcontainers/python:3.10
) is a Dev Container, it already includes a user with UID 1000.This causes the build to fail with error code 4 - UID already in use.
To Reproduce
python/packages/autogen-studio/Dockerfile
into a local directory.docker build .
Expected behavior
The Docker image should build successfully without errors.
Screenshots
N/A
Additional context
This issue is observed on the current main branch. I'm also not sure if this would be resolved as part of the ongoing effort to rewrite AutoGen Studio to AutoGen 0.4 API (#4006)
Which packages was the bug in?
AutoGen Studio (autogensudio)
AutoGen library version.
Studio 0.4.1
Other library version.
No response
Model used
No response
Model provider
None
Other model provider
No response
Python version
3.10
.NET version
None
Operating system
None
The text was updated successfully, but these errors were encountered: