Add sqry-mcp container image (Docker + Podman)#93
Closed
verivusOSS-releases wants to merge 6 commits into
Closed
Conversation
… glibc-dynamic, no static build)
…are glibc-dynamic, no static build)
…glibc-dynamic, no static build)
Member
Author
|
Closing: this targets the generated public mirror (populated by release-distribute from verivusai-labs/sqry), and it duplicates the existing internal packaging/docker/Dockerfile. Container packaging and the MCP server manifest belong in verivusai-labs/sqry, where sqry-mcp/server.json and register-mcp-registry.sh already exist. Will redirect there. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a container image for the
sqry-mcpserver (stdio, 38 tools). This unblocks the MCP-ecosystem listings that now gate on a runnable container: Glama's listing check (which the awesome-mcp-servers PR depends on) and the official MCP Registry (ocipackage type).docker/Dockerfileanddocker/Containerfile(Podman): multi-stage, install the prebuiltsqry-mcp-linux-{amd64,arm64}release binary (no full Rust/tree-sitter compile).gcr.io/distroless/cc-debian12. All 26 release assets were checked and both the fullsqryandsqry-mcpbinaries are glibc-dynamic (ldd: glibc +libstdc++6); there is no musl/static build, so distroless/cc is the minimal base carrying exactly those libs and nothing else. AFROM scratchimage would require a static build target in the release matrix.--no-daemon),SQRY_MCP_WORKSPACE_ROOT=/workspace,SQRY_REDACTION_PRESET=relativeso results are workspace-relative and map back to the host checkout.io.modelcontextprotocol.server.name=dev.sqry/sqryimage label, so a published image self-certifies to the MCP Registry as anocipackage (no crate-README marker release needed).docker/README.md: build, run, bind-mount, and MCP-client-config docs, including the--user(Docker) and rootless/:Z(Podman) notes.Verified against the v27.0.8 release binary on linux/amd64:
sqry-mcp --list-toolsreturns 38 tools,--versionreports 27.0.8, andlddshows the runtime needs only glibc +libstdc++6.Follow-ups (not in this PR): build and push the image (e.g.
ghcr.io/verivus-oss/sqry-mcp), submit it to Glama, and publishserver.jsonto the MCP Registry. A static (musl) release target would additionally enable aFROM scratchimage.