--- metaLinks: alternates: - >- https://app.gitbook.com/s/j6QEqM3Sd94bdPsX4HaN/admin/environments/add/docker/socket --- # Connect to the Docker Socket {% hint style="warning" %} Connecting to the Docker Socket is a legacy option that does not support edge features or policy management. For most use cases, [the Edge Agent is recommended](../../../../faqs/getting-started/why-do-we-recommend-using-the-edge-agent-instead-of-the-traditional-agent.md). {% endhint %} Connecting to the Docker socket directly can only be done from the local environment. Before you begin, ensure the user running the Portainer Server container has permissions to access the Docker socket. From the menu expand **Environment-related**, click **Environments**, then click **Add environment**.
Next, select **Docker Standalone** as the environment type then click **Start Wizard**. Under **More options**, select the **Socket** option and your platform. You will be shown the required parameter to pass to the Portainer container as part of your `docker run` command. Fill out the fields based on the table below.
Field/OptionOverview
NameGive the environment a descriptive name.
Override default socket pathToggle this option on to override the default /var/run/docker.sock socket path.
Socket PathIf Override default socket path is enabled, enter the path to the Docker socket.
{% hint style="info" %} Ensure that if you change the Socket Path, that you update the required bind mount parameter above to suit. {% endhint %} As an optional step you can expand the **More settings** section to categorize the environment by adding it to a [group](../../groups.md) or [tagging](../../tags.md) it for better searchability.
When you're ready, click **Connect**. If you have other environments to configure click **Continue** to proceed, otherwise click **Close** to return to the list of environments.