-
Notifications
You must be signed in to change notification settings - Fork 20
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
Registry Access Management #48
Comments
i got 0.6 version in docker, tons of containers dead, cant remove them, cant update, cannot do anything, right now, apparently ...
my real question here actually right now is: according to docs and cursor setup ( and the given command to paste ) - i do not see any skills being added. any hints or clues, on how to pop in the registry.yml ? i understand the stealth WIP state of this project, but i really want to get going with this - so appreciate ANY small insider hints, for utilizing this :-) |
@ColinMcNeil I just tried this on Windows and it didn't work so I'm going to recommend that people add the vonwig namespace to their RAM config and see if that works on Windows. |
For users of Registry Access Management that may not be able to pull public images unless they are stored in the docker namespace (eg internal users dog-fooding the enterprise login), we can not demo features that require the
mcp/docker
to pull new public tools from other repos likevonwig
.For demoing internally, this has been an issue. Let's switch to use /var/run/docker.raw.sock, which does not proxy through the external socket where registry access is enforced.
This means that the Claude Desktop configuration and gordon configurations need to include additional
docker run
optionsI tested this on macos by deleting every image and then starting Claude Desktop and going through a bunch of our prompt flows.
This needs two things to be usable.
The text was updated successfully, but these errors were encountered: