Skip to content

Add rootless Docker support and update documentation#1549

Draft
sireeshajonnalagadda wants to merge 9 commits intodevcontainers:mainfrom
sireeshajonnalagadda:rootless_socket
Draft

Add rootless Docker support and update documentation#1549
sireeshajonnalagadda wants to merge 9 commits intodevcontainers:mainfrom
sireeshajonnalagadda:rootless_socket

Conversation

@sireeshajonnalagadda
Copy link
Contributor

@sireeshajonnalagadda sireeshajonnalagadda commented Jan 29, 2026

This PR fixes the issue for rootless docker

  • Introduced socketPath option for custom Docker socket configuration in README and devcontainer-feature.json.
  • Updated install script to accommodate rootless Docker socket paths.
  • Added tests for rootless Docker configurations and custom socket paths.
  • Created new documentation for rootless Docker setups and scenarios.
    Checklist
    Changes works as expected for both root and rootless docker environments.

@sireeshajonnalagadda sireeshajonnalagadda marked this pull request as ready for review February 17, 2026 05:32
@sireeshajonnalagadda sireeshajonnalagadda requested a review from a team as a code owner February 17, 2026 05:32
@sireeshajonnalagadda sireeshajonnalagadda marked this pull request as draft March 5, 2026 06:09
Copy link
Contributor

@Kaniska244 Kaniska244 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @sireeshajonnalagadda

I have left few comments. Please get back in case of any issues.

buildx=(docker-buildx-plugin)
fi
apt-get -y install --no-install-recommends ${cli_package_name}${cli_version_suffix} "${buildx[@]}" docker-compose-plugin
if [ "${DOCKER_DASH_COMPOSE_VERSION}" != "v1" ]; then
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the relevance of this check for rootless Docker support?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we have this documentation in the test directory? If any change required, couldn't this be done in the readme file or even as PR comment if applicable?

],
"containerUser": "vscode"
},
"xdg_runtime_dir_socket": {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we really need this test when it appears to be quite similar to rootless_docker_socket scenario?

"moby": false
}
},
"mounts": [
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we really need the explicit mounts for this case as I guess this should be the default behavior. isn't it?

},
"installDockerComposeSwitch": {
"type": "boolean",
"default": true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although not quite related to this PR, can we make this flag as false by default to align the behavior with the d-in-d feature? This is because the compose-switch component which is installed using this flag is obsolete and not really required by default as the docker compose v2 is the default configuration for the feature.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants