Activity

1. MurzNN commented on Dec 8, 2021

   

   Alexey Murz Korepov (MurzNN)

   on Dec 8, 2021

   Author

   More actions

   Now we have nerdctl as a Docker-compatible CLI for containerd, maybe we can reuse it instead of docker backend to manage container operations for VS Code Remote Containers extension?

   🎉React with 🎉2Reacted by RedAtman and Kaustubh Badrike
2. github-actions

   added

   containersIssue in vscode-remote containersIssue in vscode-remote containers

   on Dec 8, 2021
3. MurzNN commented on Dec 8, 2021

   

   Alexey Murz Korepov (MurzNN)

   on Dec 8, 2021

   Author

   More actions

   Removing Dockershim and Docker support from Kubernetes is scheduled for Kubernetes v1.24.
4. chrmarti commented on Dec 10, 2021

   

   Christof Marti (chrmarti)

   on Dec 10, 2021

   Contributor

   More actions

   You can use a Docker compatible CLI by changing this setting:
   

   When I tried nerdctl with lima a while ago, it looked like it was not fully compatible with the Docker CLI yet.
5. Christof Marti (chrmarti)

   self-assigned this

   on Dec 10, 2021
6. Christof Marti (chrmarti)

   added this to the Backlog milestone on Dec 10, 2021
7. Christof Marti (chrmarti)

   added

   feature-requestRequest for new features or functionalityRequest for new features or functionality

   on Dec 10, 2021
8. Chuxel commented on Dec 15, 2021

   

   Chuck Lantz (Chuxel)

   on Dec 15, 2021

   Last edited by Chuxel

   Member

   More actions

   We should make this more specific about nerdctl. Updating the subject.

   Remote - Containers does not touch container engines or daemons directly but rather interacts with CLIs. It makes no assumptions about how the engine functions. There's no "containerd, CRI-O" CLI per-se. For example, Docker itself uses containerd on Linux, so really it's already supported. Dockershim going away will not have any affect.

   The issue is that each CLI that needs to be supported will require separate work unless it supports everything the docker CLI does with the same arguments. Podman is closest but there are always nuances.

   While the nerdctl CLI is part of the containerd project, it currently has gaps most notably around the missing --mount property that has replaced -v and automatic creation of named volumes in either syntax (nerdctl requires a separate command be called). Would love to see those gaps resolved.
9. Chuck Lantz (Chuxel)

   changed the title [-][Containers] Connecting VS Code Remote to container runtimes other than Docker (containerd, CRI-O)[/-] [+][Containers] Support using nerdctl to connect to a container backend[/+] on Dec 15, 2021
10. MurzNN commented on Dec 16, 2021

    

    Alexey Murz Korepov (MurzNN)

    on Dec 16, 2021

    Author

    More actions

    nerdctl is only one option, most easier to integrate (because of Docker compatibility), but we have also crictl that must give compatibility with any CRI-compatible container engine!

    So maybe split the issue to 2 parts - nerdctl and crictl?
11. Chuck Lantz (Chuxel)

    changed the title [-][Containers] Support using nerdctl to connect to a container backend[/-] [+][Containers] Support using nerdctl to connect to a containerd backend[/+] on Dec 16, 2021
12. Chuxel commented on Dec 16, 2021

    

    Chuck Lantz (Chuxel)

    on Dec 16, 2021

    Member

    More actions

    We should track crictl as a separate issue. Each CLI will be a separate effort. Raised #6075

    👍React with 👍2Reacted by Alexey Murz Korepov and Avery Freeman
13. Chuxel commented on Oct 12, 2022

    

    Chuck Lantz (Chuxel)

    on Oct 12, 2022

    Last edited by Chuxel

    Member

    More actions

    FYI - For those not aware, the dev container CLI is now open source and is what the extension uses to interoperate with container engines if anyone has interest in contributing. https://github.com/devcontainers/cli

    🎉React with 🎉3Reacted by Sander Maijers, Peter Roberts and Braxton Beyer
14. Anutrix commented on Mar 28, 2023

    

    Numan Zaheer Ahmed (Anutrix)

    on Mar 28, 2023

    More actions

    Any updates on this?

    👍React with 👍2Reacted by Dariusz Antoniuk and Joe Bowbeer

    👀React with 👀14Reacted by inliquid, Joe Bowbeer, Sampath Sukesh Ravolaparthi, CasperX, Christopher Mullarkey, Zvika Almog, Lina, Jan Nemcik, Lucas Mello, Jordan Peterson and 4 more
15. kidbrax commented on Dec 14, 2023

    

    Braxton Beyer (kidbrax)

    on Dec 14, 2023

    More actions

    FYI - For those not aware, the dev container CLI is now open source and is what the extension uses to interoperate with container engines if anyone has interest in contributing. https://github.com/devcontainers/cli

    Chuck Lantz (@Chuxel) I checked the devcontainers/cli repo and searched for APIVersion and got no results. This leads me to believe the change we need is not in that repo, since the command VSCode runs when spinning up a devcontainer (when trying finch) is finch version --format {{.Server.APIVersion}}.

    Is the code for this extension not open? This repo is just for feedback, correct?
16. Chuxel commented on Dec 14, 2023

    

    Chuck Lantz (Chuxel)

    on Dec 14, 2023

    Member

    More actions

    FYI - For those not aware, the dev container CLI is now open source and is what the extension uses to interoperate with container engines if anyone has interest in contributing. https://github.com/devcontainers/cli

    @Chuxel I checked the devcontainers/cli repo and searched for APIVersion and got no results. This leads me to believe the change we need is not in that repo, since the command VSCode runs when spinning up a devcontainer (when trying finch) is finch version --format {{.Server.APIVersion}}.

    Is the code for this extension not open? This repo is just for feedback, correct?

    Yeah, I'd recommend opening an issue in the CLI repository to discuss the specific scenario you are looking into.

    Christof Marti (@chrmarti) is the version check in the CLI or extension? Generally, seems like these kinds of checks should end up in the CLI (if not the broader spec) so they can be contributed, but I'm not sure if this is a proposed feature.
17. chrmarti commented on Dec 18, 2023

    

    Christof Marti (chrmarti)

    on Dec 18, 2023

    Contributor

    More actions

    The version check is in the extension. Making that more tolerant now.

    👍React with 👍1Reacted by Josh Samuel

    ❤️React with ❤️1Reacted by Braxton Beyer
18. jsamuel1 commented on Jan 2, 2024

    

    Josh Samuel (jsamuel1)

    on Jan 2, 2024

    Last edited by jsamuel1

    More actions

    nerdctl and finch also don't support --sig-proxy=false
    This appears to be a fixed parameter in devcontainer when using single-container devcontainer configurations.
    https://github.com/containerd/nerdctl/blob/main/docs/command-reference.md#whale-nerdctl-attach

    (Offending Line in devcontainer code: https://github.com/devcontainers/cli/blob/f7d4c853bf8c284d784173f3e915a34d961b0b55/src/spec-node/singleContainer.ts#L396 )

    👍React with 👍1Reacted by Richard Natal
19. chrmarti commented on Jan 9, 2024

    

    Christof Marti (chrmarti)

    on Jan 9, 2024

    Contributor

    More actions

    I'm hesitant to make details like --sig-proxy=false conditional on the detected CLI as that might quickly become a long list of cases to distinguish given the growing list of Docker-like CLIs.

    The more tolerant version check is available in Dev Containers extension 0.330.0-pre-release.
20. Bigous commented on Jan 18, 2024

    

    Richard Natal (Bigous)

    on Jan 18, 2024

    Last edited by Bigous

    More actions

    I'm hesitant to make details like --sig-proxy=false conditional on the detected CLI as that might quickly become a long list of cases to distinguish given the growing list of Docker-like CLIs.

    Hi Christof Marti (@chrmarti) ,

    In this case, for docker, you are tuning off the feature... and this feature doesn't even exists in nerdctl... you can safely be "non conditional" just detecting you are using nerdctl (which it already do) and not sending the argument.

    Could that be a solution?
21. CodeChanning commented on Jun 25, 2024

    

    Channing Gaddy (CodeChanning)

    on Jun 25, 2024

    More actions

    A --sig-proxy change was merged to nerdctl yesterday that should supports the flag in run
    containerd/nerdctl#3043

    👀React with 👀1Reacted by Christopher Mullarkey
22. midnight-wonderer commented on Feb 11, 2025

    

    Sarun Rattanasiri (midnight-wonderer)

    on Feb 11, 2025

    More actions

    I tried substituting the docker command with nerdctl using the --docker-path option.
    The issue I encountered was with the additional_contexts support detection logic, and possibly also with parseVersion.

    The CLI always determined that nerdctl compose was unsupported, which caused the build to fail.

    ERROR [internal] load metadata for docker.io/library/dev_container_feature_content_temp:latest

    For reference, my nerdctl is integrated with version 0.19:

     buildctl:
      Version:	0.19.0
    

    I wish the docker compose module of the CLI to be refactored into a class, so we can inject the differences as functions into the constructor (or extract the differences to the constructor).
23. cmullark commented on Apr 18, 2025

    

    Christopher Mullarkey (cmullark)

    on Apr 18, 2025

    More actions

    I tried this today with version 0.409.0 of this extension with finch, which uses nerdctl, instead of docker and I am able to spin up a devcontainer!

    Not sure where the rough edges are yet but this is now possible today.

    👍React with 👍1Reacted by Victor Stanescu
24. subesokun commented on Apr 23, 2025

    

    Subesokun (subesokun)

    on Apr 23, 2025

    More actions

    Finch's devcontainer Mac integration worked for me: https://runfinch.com/docs/integrations/mac/devcontainers. Consider tweaking the default config (cups, memory, ...): https://runfinch.com/docs/configuration-reference/.