starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Docker not working in Ubuntu Terminal #3891

New Issue
Closed
opened 2026-01-30 23:32:37 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 23:32:37 +00:00
Owner
Copy Link

Originally created by @anandijain on GitHub (Sep 16, 2019).

Environment

Windows Terminal (Preview)
Version: 0.4.2382.0
Microsoft Windows [Version 10.0.18362.356]

Docker

Steps to reproduce

I installed docker via sudo apt-get, following this guide.

However, sudo systemctl start docker gives me the following error:
System has not been booted with systemd as init system (PID 1). Can't operate.

Other people said that sudo service docker start would work but that gives:
* Starting Docker: docker

Which looks fine, but when running any docker run command, I get:

docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.40/containers/create: dial unix /var/run/docker.sock: connect: permission denied.
See 'docker run --help'.

Expected behavior

I am expecting to have docker start up and run in the terminal.

Actual behavior

The actual behavior is that I get permission denied when connecting to the Docker daemon

Originally created by @anandijain on GitHub (Sep 16, 2019). # Environment ``` Windows Terminal (Preview) Version: 0.4.2382.0 Microsoft Windows [Version 10.0.18362.356] ``` Docker # Steps to reproduce I installed docker via `sudo apt-get`, following [this guide](https://docs.docker.com/install/linux/docker-ce/ubuntu/). However, `sudo systemctl start docker` gives me the following error: `System has not been booted with systemd as init system (PID 1). Can't operate.` Other people said that `sudo service docker start` would work but that gives: `* Starting Docker: docker` Which looks fine, but when running any `docker run` command, I get: ``` docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.40/containers/create: dial unix /var/run/docker.sock: connect: permission denied. See 'docker run --help'. ``` # Expected behavior I am expecting to have docker start up and run in the terminal. # Actual behavior The actual behavior is that I get permission denied when connecting to the Docker daemon
claunia added the Needs-TriageResolution-ExternalNeeds-Tag-Fix labels 2026-01-30 23:32:37 +00:00
claunia commented 2026-01-30 23:32:38 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 16, 2019):

This is not a terminal issue. Please ask on the Docker forums or the WSL repository.

@DHowett-MSFT commented on GitHub (Sep 16, 2019): This is not a terminal issue. Please ask on the Docker forums or the [WSL repository](https://github.com/microsoft/wsl).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Tag-Fix Needs-Triage Resolution-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#3891
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?