docker / copilot-issues Goto Github PK

Today, we support node, Java and node projects. We should expand support to cover Go as well.

Today, we support node, Java and node projects. We should expand support to cover .NET as well.

Until we can add a full docs integration, we should try to prevent Copilot from hallucinating

Until there's a better API, we should print out some examples when users say "Hi" or "What can I do?"

These are some basic questions that we should see how these are handled by Copilot without Docker and determine if we should handle these scenarios.

• @docker what is the best way to Dockerize this project
• @docker how do I create a Dockerfile for this project
• @docker how do I create a Docker Compose file for this project
• @docker create build stage that installs dependencies
• @docker add a health check to the Dockerfile
• @docker add a volume to the Docker Compose file
• @docker I'm getting a syntax error in this Dockerfile
• @docker fix the indentation in this Docker Compose file
• @docker why won't this build command work
• @docker what base image should I use for this project
• @docker how do I optimize this Dockerfile
• @docker how can I run my tests in a Docker container

I want to be able to ask @docker to generate the right Docker assets for me to start building a new project. For example:

@docker can you help me create Docker assets to spin up an app in containers for local development? I want to build an app with a React frontend, Python backend, and Postgres db.

Today, this doesn't work, but it'd be cool if it could leverage the same templates we're using for brownfield projects and scaffold the app for local dev. I'd probably also expect it to create the subdir structure at the same time so something like this:

my new app!
│   docker-compose.yml
│	README.md
└───frontend
│   │  Dockerfile
│   │  .dockerignore
└───api
    │   Dockerfile
    │   .dockerignore

The README could include instructions on how to run the docker-compose.yml etc.

As a user, I should be able to have access to all content on docs.docker.com via the Docker extension for GitHub Copilot

Environment data

• Client (e.g. github.com, VS Code, Codespaces, JetBrains): all

Repro Steps

1. Ask the agent to containerize a repo it doesn't have permissions to access

Expected behavior

A decent error message

Actual behavior

Request gets proxied to copilot and the user doesn't know they need to authorize the GH app to access the repo in question

Extra details

When the GH app doesn't have the appropriate permissions, GH will return to our agent a "redacted reference" (type: github.redacted).
We should recognize this situation and handle it appropriately

We should be able to handle the same languages supported by Copilot LLM.

Users should be able to authenticate with their Docker credentials to make full use of their subscription via Copilot

We can enable a reproducible and proactive developer experience by generating a GHA workflow with Docker Scout.

As part of this, we should configure the right the repo secrets/variables for auth with user's consent so that we make this a seamless experience.

Today, we provide a "teaser trailer" for Scout for unauthenticated users (show top 2 vulns and then tell them how to continue in CLI).

The docker scout recommendations command display recommendations for base images updates. It analyzes the image and display recommendations to refresh or update the base image. For each recommendation it shows a list of benefits, such as fewer vulnerabilities or smaller image size.