Skip to content

【Feat】Automate Docker Image Builds with GitHub Actions#2466

Closed
QwertyJack wants to merge 2 commits intoanthropics:mainfrom
QwertyJack:main
Closed

【Feat】Automate Docker Image Builds with GitHub Actions#2466
QwertyJack wants to merge 2 commits intoanthropics:mainfrom
QwertyJack:main

Conversation

@QwertyJack
Copy link

Description:

This PR introduces a new GitHub Actions workflow to automate the Docker image build process. This workflow is configured to automatically trigger whenever the branch is updated, ensuring that a fresh Docker image is built for the latest code.

Key Changes:

  • Added GitHub Actions Workflow: A new workflow file (.github/workflows/docker-build.yml or similar) has been added.
  • Leverages GitHub Action Templates: The workflow is based on existing GitHub Action templates for Docker image building, ensuring best practices and ease of maintenance.
  • Automated Trigger: The workflow is set to run automatically on push events to the branch, providing continuous integration for Docker image creation.

Benefits:

  • Continuous Integration: Ensures that a Docker image is always up-to-date with the latest code changes.
  • Improved Reliability: Catches build issues early in the development cycle.
  • Reduced Manual Effort: Eliminates the need for manual Docker image builds.
  • Faster Feedback Loop: Developers get immediate feedback on the Docker build status of their changes.

How to Test:

Push a new commit to this branch, and observe the GitHub Actions tab to confirm the workflow is triggered and completes successfully.

Related Issues: NA

@ant-kurt ant-kurt self-requested a review July 29, 2025 20:40
@QwertyJack
Copy link
Author

@ant-kurt pls

@ant-kurt
Copy link
Collaborator

ant-kurt commented Aug 2, 2025

@QwertyJack thanks for creating this PR - we're talking over a few things internally and have not forgotten this!

@QwertyJack QwertyJack force-pushed the main branch 5 times, most recently from fcf39a3 to 81e8547 Compare August 16, 2025 15:35
QwertyJack and others added 2 commits August 19, 2025 05:00
Build and push devcontainer docker image to ghcr.io
- Add support for linux/amd64 and linux/arm64 platforms
- Include main and latest tags for improved container distribution

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@ant-kurt
Copy link
Collaborator

Hi - we're not currently planning to officially support a published devcontainer image right now, and if we did it would likely not be one for the Node.js toolchain specifically. We may revisit this decision in the future; note that if we were to publish images, they would likely be derived from the well-known prebuilt devcontainer images.

Thank you for creating this and please keep the feedback coming regarding devcontainers (and Claude Code generally).

@ant-kurt ant-kurt closed this Aug 19, 2025
tpitre added a commit to southleft/figma-console-mcp that referenced this pull request Feb 3, 2026
Claude Code's native --transport sse command has a bug where the OAuth
flow completes successfully but the connection fails to reconnect
afterwards (see anthropics/claude-code#2466).

Documentation changes:
- README: Add warning and mcp-remote workaround for Claude Code
- docs/setup.md: Add Claude Code section with workaround
- docs/troubleshooting.md: Add dedicated section for this issue

Server changes (src/index.ts):
- Add MCP OAuth spec-compliant endpoints for mcp-remote compatibility
- Add /.well-known/oauth-protected-resource (RFC9728)
- Add /authorize, /token, /oauth/register endpoints
- Add Bearer token validation on /sse endpoint
- These changes enable mcp-remote to work as the workaround
@pravorskyi
Copy link

Hi, @QwertyJack! I have implemented automatic rebuilding of devcontainer images, thanks to your PR which inspired me.

The image is updated automatically without any changes to the original Dockerfile, every time a .devcontainer is released or when a new version of Claude Code is released (checked once a day).

Until Anthropic starts official support, I decided to automate the build for all enthusiasts.

https://github.com/pravorskyi/claude-code-devcontainer

https://github.com/users/pravorskyi/packages/container/package/claude-code-devcontainer%2Fdevcontainer

Example how it can be used:

FROM ghcr.io/pravorskyi/claude-code-devcontainer/devcontainer:latest

# Example: add Python tooling
USER root
RUN apt-get update && apt-get install -y --no-install-recommends \
    python3-dev build-essential python3-venv \
    && apt-get clean && rm -rf /var/lib/apt/lists/*

ENV VIRTUAL_ENV=/opt/venv
COPY requirements.txt /opt
RUN python3 -m venv "$VIRTUAL_ENV" && \
    . "$VIRTUAL_ENV/bin/activate" && \
    pip install --no-cache-dir -r /opt/requirements.txt
ENV PATH="$VIRTUAL_ENV/bin:$PATH"

USER node
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants