Docker desktop on windows server 2022 in AWS Ec2 instance

Anshul Kapoor · 2024-01-21T21:23:51Z

Hi, i tried the instructions you have me tioned in the video but I am getting the error while installing the package Command 1. Install-Module -Name DockerMsftProvider -Force 2. Install-Package -Name docker -ProviderName DockerMsftProvider error - Cannot find the path

Last Post

RSS

Posts: 8

Anshul Kapoor

Topic starter

Jan 23, 2024 10:25 pm

(@anshulkapoor)

Active Member

Joined: 2 years ago

yes, we are trying to test the application on widows server before deplying to AWS ECS

new issue

i have installed the dockerusing below command in powershell as administrator

only user who are part of administrator group can ablw to run the docker command

.\install-docker-ce.ps1

but user who are added in remote desktop user are not able run docker commands and getting access denied error

And when remote desktop user run powershell as administrator they got an error @The app has been blocked by your administrator

How we can give access to remote user to access powershell as administrator withour adding them in admin group

i am attaching both the error for your reference

.\install-docker-ce.ps1

1 Reply

Brandon Lee

Admin

(@brandon-lee)

Joined: 15 years ago

Member

Posts: 580

Jan 24, 2024 12:23 pm

Reply to

Anshul Kapoor

@anshulkapoor I did some digging on this one. The issue relates to permissions to the Docker daemon. I was able to reproduce your error on a Windows Server 2022 host I have in my lab environment.

The solution involves just a few steps. First, you need to create the local Windows group docker-users. Then place the user you want to be able to run Docker in this group.

Next, you need to create a daemon.json file in this path: C:\ProgramData\docker\config. The contents of the file will contain the following:

{
    "group": "docker-users"
}

Save the file with those contents, and then restart your Docker Engine:

Now, you should be able to run Docker commands as an underprivileged user without the need to launch PowerShell as an admin:

Posts: 8

Anshul Kapoor

Topic starter

Jan 24, 2024 1:17 pm

(@anshulkapoor)

Active Member

Joined: 2 years ago

i have verified these steps and found these already exist. Please find attached screenshot.

the inlt difference is these are AD user not the local user. Does that create any difference?

1 Reply

Brandon Lee

Admin

(@brandon-lee)

Joined: 15 years ago

Member

Posts: 580

Jan 24, 2024 1:22 pm

Reply to

Anshul Kapoor

@anshulkapoor I will test on my side as well and see if it makes a difference with domain users.

Posts: 8

Anshul Kapoor

Topic starter

Jan 24, 2024 2:41 pm

(@anshulkapoor)

Active Member

Joined: 2 years ago

Thanks the daemon.json config was like this before attached screen shot

i tried both ways host and adding tcp and only with group as well

both ways its not working

1 Reply

Brandon Lee

Admin

(@brandon-lee)

Joined: 15 years ago

Member

Posts: 580

Jan 24, 2024 9:38 pm

Reply to

Anshul Kapoor

@anshulkapoor I have tested with a domain user who is a non-admin added to the local "docker-users" group, and it works for me.

Just curious, are you sure the Docker service was restarted after creating and making the changes to the daemon.json file?

Posts: 8

Anshul Kapoor

Topic starter

Jan 24, 2024 10:37 pm

(@anshulkapoor)

Active Member

Joined: 2 years ago

Yes I restarted the service and reboot the server as well but not working

when I added the domain user into adminstrator it is working fine.

2 Replies

Anshul Kapoor

(@anshulkapoor)

Joined: 2 years ago

Active Member

Posts: 8

Jan 24, 2024 10:51 pm

Reply to

Anshul Kapoor

Also prior to command line docker installation I was trying to install docker desktop in windows server 2022 was might be conflicting with docker user

Brandon Lee

Admin

(@brandon-lee)

Joined: 15 years ago

Member

Posts: 580

Jan 25, 2024 8:19 am

Reply to

Anshul Kapoor

@anshulkapoor That could be. Do you still show Docker Desktop installed on the Server in programs and features currently? Also, have you tested with a non-admin local user? Do you see the same behavior?

Posts: 580

Brandon Lee

Admin

Jan 25, 2024 12:43 pm

(@brandon-lee)

Member

Joined: 15 years ago

@anshulkapoor also, you can use Process monitor from Sysinternals to see where the exact Access Denied entries are coming from.

https://learn.microsoft.com/en-us/sysinternals/downloads/procmon

Logged in as an administrator in one session on your server, start a process monitor capture. Try to run a Docker command where you see the error in another session for an end-user.

Once the error happens, stop the Process Monitor capture. Then search for "access denied" using the search function.

This should allow seeing what is getting the permissions error. Note there may be several entries in the results.

Like this:

Recent Posts