Add Configuration Option for Docker Privileged Access in Runtime

[iamrahultanwar]

Currently, running Docker-in-Docker (DinD) scenarios requires privileged access to be explicitly set at container startup. This feature request proposes adding the ability to configure privileged access through the Docker runtime configuration, making it more flexible and manageable for specific use cases.

[runabol]

Mind providing a sample docker cli command of the kind of privilege you're looking to have?

[iamrahultanwar]

@runabol

I have this docker image that i am using to run some services using supabase, supabase cli internally uses docker to run its services, to make that i am using dind setup. But challenge here is that running dind we need to run it as --privileged access. Without the the docker demon never starts with in the dind environment

https://github.com/cruizba/ubuntu-dind?tab=readme-ov-file#3-usage-guide

FROM cruizba/ubuntu-dind:latest

# Install dependencies
RUN apt-get update && apt-get install -y \
    git \
    curl \
    bash

# Set up environment for NVM
ENV NVM_DIR /root/.nvm
ENV NODE_VERSION 22.13.0

# Install NVM, Node.js, and verify installation
RUN curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.1/install.sh | bash \
    && . $NVM_DIR/nvm.sh \
    && nvm install $NODE_VERSION \
    && nvm alias default $NODE_VERSION \
    && nvm use default

# Add NVM and Node.js to PATH
ENV PATH $NVM_DIR/versions/node/v$NODE_VERSION/bin:$PATH

# Verify installations (this will be shown during build)
RUN node -v && \
    npm -v

RUN npx supabase start -> supabase needs docker to run its services locally