Powershell Console for Windows, run as Administrator

[ncresswell]

When starting the Powershell Console of a Windows Server Core Container, the session is started in "user context", which means you are unable to run any privileged actions. You cannot elevate to Administrator from within Powershell.

We need to find a way to start powershell with elevated permissions

[deviantony]

Can't you just specify Administrator in the user field?

[deviantony]

As we're limited by the Docker API usage here, we need to figure out how this can be done via the Docker API (check if it's available when using the Docker CLI as well).

[ncresswell]

Well the user is actually ContainerAdministrator, but no, that doesnt work Rgds, Neil Cresswell On 4/09/2017, at 7:35 PM, Anthony Lapenna <[email protected]<mailto:[email protected]>> wrote: Can't you just specify Administrator in the user field? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_1170-23issuecomment-2D326887704&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=NSLTTNenymZAW_WT5JnoZ1CMMtfXiW5urSwHFUMVJr4&s=zsFAzQaAOugO4_zhKchrIeBmW-WHkpomU9MntuMfWk4&e=>, or mute the thread<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AWGrlV0fOsKcxQfvPslj-5F6pBdwDmTDrnks5se6g6gaJpZM4PLTM3&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=NSLTTNenymZAW_WT5JnoZ1CMMtfXiW5urSwHFUMVJr4&s=IJPp6dlbX3EkHqNc6er0lXPdDxLHE2Bj-PGqWZcQopM&e=>.

[yassirh]

@ncresswell I have just tried to run as Administrator and ended up with ContainerAdministrator :

[olljanat]

@yassirh On Windows Server 2016 and its Docker images default is ContainerAdministrator but on semi-annual channel versions 1709 and 1803 and on just released Windows Server 2019 ContainerUser is default.

So probably it would be good idea to fix this now when more and more uses will start migrate to Windows Server 2019 and see this issue.

EDIT: It is also possible to change user on Dockerfile like we do with Portainer https://github.com/portainer/portainer/blob/develop/build/windows/nanoserver/Dockerfile#L3 but that should be only used with containers which really need it.

[olljanat]

@yassirh I did some more testing with this. By writing username ContainerAdministrator to user field works fine so it can be set as a default for Windows but we need implement Windows version checking to this one because Windows Server 2016 does not support to specify username even on docker exec command and starting console will fail if on that scenario.

[stale[bot]]

This issue has been marked as stale as it has not had recent activity, it will be closed if no further activity occurs in the next 7 days. If you believe that it has been incorrectly labelled as stale, leave a comment and the label will be removed.

[stale[bot]]

Since no further activity has appeared on this issue it will be closed. If you believe that it has been incorrectly closed, leave a comment and mention @itsconquest. One of our staff will then review the issue.
Note - If it is an old bug report, make sure that it is reproduceable in the latest version of Portainer as it may have already been fixed.

[ghost]

Re-opening this as it should not be closed