8000 LCOW: Invalid Platform OS "linux" · Issue #2241 · docker/for-win · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

LCOW: Invalid Platform OS "linux" #2241

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
1 of 2 tasks
necroTaxonomist opened this issue Jul 23, 2018 · 17 comments
Closed
1 of 2 tasks

LCOW: Invalid Platform OS "linux" #2241

necroTaxonomist opened this issue Jul 23, 2018 · 17 comments
Labels
lifecycle/locked version/10.0 14393 version/10.0 16299 version/10.0 17134 version/18.03.0-ce-win59

Comments

@necroTaxonomist
Copy link
necroTaxonomist commented Jul 23, 2018 •
edited
Loading
  • I have tried with the latest version of my channel (Stable or Edge)
  • I have uploaded Diagnostics
  • Diagnostics ID: 3ED176A3-2D7C-42BE-B181-E05843FEA108/2018-07-23_14-05-48

Expected behavior

Build a Linux image for CentOS 6.8 while using Windows containers

Actual behavior

Unable to pull the image or build.
Returns an error saying:

Error response from daemon: invalid platform: invalid platform os "linux"

Information

  • Windows Version: Windows 10 Enterprise Version 10.0.14393 Build 14393
  • Docker for Windows Version: Version 18.03.0-ce-win59 (16762)

I'm working on a project that requires running both Linux containers and Windows containers at the same time. I'm not using the most recent version of Docker in this channel, because that version crashes whenever I switch to Windows containers (#1898).

Steps to reproduce the behavior

  1. Start Docker for Windows
  2. Switch to using Windows containers
  3. Enable Experimental features in the Docker settings
  4. In command line, run docker pull --platform=linux centos:6.8
@necroTaxonomist
Copy link
Author
necroTaxonomist commented Jul 26, 2018 •
edited
Loading

Downloaded 18.03.0-ce-win72 and now I just get an "unsupported os linux"

Has the experimental feature been removed?
8000

@ebriney
Copy link
Member
ebriney commented Jul 27, 2018

Hi @necroTaxonomist. Yes, you have to enable experimental in the daemon settings. We disabled it because if you pull an lcow image and disable experimental, it bricks your windows daemon...

@ebriney ebriney closed this as completed Jul 27, 2018
@necroTaxonomist
Copy link
Author

@ebriney I do have experimental settings enabled. Or at least, the checkbox is checked, and I see it in windows-daemon-options.json

@ebriney
Copy link
Member
ebriney commented Jul 27, 2018

And when you do docker info you see lcow graphdriver?

@necroTaxonomist
Copy link
Author

No, I don't see that option. Is that something separate I need to turn on?

@ebriney
Copy link
Member
ebriney commented Jul 27, 2018

Can you dump your docker info?
Have you switch on windows containers? --platform=linux is only valid with windows daemon.

@necroTaxonomist
Copy link
Author 
Containers: 2
 Running: 1
 Paused: 0
 Stopped: 1
Images: 13
Server Version: 18.06.0-ce
Storage Driver: windowsfilter
 Windows: 
Logging Driver: json-file
Plugins:
 Volume: local
 Network: ics l2bridge l2tunnel nat null overlay transparent
 Log: awslogs etwlogs fluentd gelf json-file logentries splunk syslog
Swarm: inactive
Default Isolation: hyperv
Kernel Version: 10.0 14393 (14393.2368.amd64fre.rs1_release_inmarket_aim.180712-1833)
Operating System: Windows 10 Enterprise Version 1607 (OS Build 14393.2368)
OSType: windows
Architecture: x86_64
CPUs: 8
Total Memory: 7.922GiB
Name: 327-Z240-3
ID: GODZ:GMRK:27BA:RMEU:HQFH:YDRD:73UM:H7VO:CIJF:LRXS:6F34:WT4I
Docker Root Dir: C:\ProgramData\Docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: -1
 Goroutines: 46
 System Time: 2018-07-27T10:38:06.1273738-04:00
 EventsListeners: 2
Registry: https://index.docker.io/v1/
Labels:
Experimental: true
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

@ebriney
Copy link
Member
ebriney commented Jul 27, 2018

Oh, lcow is supported on Windows RS3 (16299) and above only.

@necroTaxonomist
Copy link
Author

Oh, thanks. Good to know I guess.

@chanseokoh
Copy link
chanseokoh commented Sep 10, 2018 •
edited
Loading

@ebriney I'm seeing the same error. I am trying docker pull --platform linux registry:2 on Windows.

Oh, lcow is supported on Windows RS3 (16299) and above only.

I don't get what the number 16299 means. Below is my system. Does it not support --platform linux either?

Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 2
Server Version: 18.03.1-ce
Storage Driver: windowsfilter
 Windows: 
Logging Driver: json-file
Plugins:
 Volume: local
 Network: ics l2bridge l2tunnel nat null overlay transparent
 Log: awslogs etwlogs fluentd gelf json-file logentries splunk syslog
Swarm: inactive
Default Isolation: process
Kernel Version: 10.0 14393 (14393.2430.amd64fre.rs1_release_inmarket_aim.180806-1810)
Operating System: Windows Server 2016 Datacenter
OSType: windows
Architecture: x86_64
CPUs: 4
Total Memory: 15GiB
Name: kokoro-winserver2016-v1
ID: XHOF:TYNO:OL2D:YS5E:J63Z:FMMU:3ZDS:BHTX:BXAB:25MB:FGN4:MQHR
Docker Root Dir: C:\ProgramData\Docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: true
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

@mat007
Copy link
Member
mat007 commented Sep 11, 2018

@chanseokoh 16299 is the build number of your Windows system, here yours is

Kernel Version: 10.0 14393 (14393.2430.amd64fre.rs1_release_inmarket_aim.180806-1810)

i.e. 14393

@chanseokoh chanseokoh mentioned this issue Sep 11, 2018
Open
@Mostafa-Armandi
Copy link

Hi
Mine is as below but the same issue :
Is there any solution?

Client:
 Debug Mode: false
 Plugins:
  buildx: Build with BuildKit (Docker Inc., v0.2.2-10-g3f18b65-tp-docker)
  app: Docker Application (Docker Inc., v0.8.0)

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 Server Version: 19.03.1
 Storage Driver: windowsfilter
  Windows:
 Logging Driver: json-file
 Plugins:
  Volume: local
  Network: ics l2bridge l2tunnel nat null overlay transparent
  Log: awslogs etwlogs fluentd gcplogs gelf json-file local logentries splunk syslog
 Swarm: inactive
 Default Isolation: hyperv
 Kernel Version: 10.0 16299 (16299.637.amd64fre.rs3_release_svc.180808-1748)
 Operating System: Windows 10 Enterprise Version 1709 (OS Build 16299.1331)
 OSType: windows
 Architecture: x86_64
 CPUs: 4
 Total Memory: 11.9GiB
 Name: Armandi-PC
 ID: EVS4:CARH:QOOA:OQ2T:TT2R:4DLH:CIIQ:ZMHL:DJGB:GQMG:K3YA:JH3T
 Docker Root Dir: C:\ProgramData\Docker
 Debug Mode: true
  File Descriptors: -1
  Goroutines: 30
  System Time: 2019-08-26T19:36:51.197303+04:30
  EventsListeners: 2
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: true
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
 Product License: Community Engine

@cowlinator
Copy link
cowlinator commented Aug 29, 2019 •
edited
Loading

I am also getting this error with Windows 10 (17134), which is greater than 16299

Client:
 Debug Mode: false

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 Server Version: 19.03.1
 Storage Driver: windowsfilter
  Windows:
 Logging Driver: json-file
 Plugins:
  Volume: local
  Network: ics l2bridge l2tunnel nat null overlay transparent
  Log: awslogs etwlogs fluentd gcplogs gelf json-file local logentries splunk syslog
 Swarm: inactive
 Default Isolation: hyperv
 Kernel Version: 10.0 17134 (17134.1.amd64fre.rs4_release.180410-1804)
 Operating System: Windows 10 Enterprise Version 1803 (OS Build 17134.950)
 OSType: windows
 Architecture: x86_64
 CPUs: 12
 Total Memory: 15.86GiB
 Name: US9CB6D06C60FF
 ID: HMSJ:4W74:4R3L:5XCI:KDKA:XI45:BJEQ:CBXY:74VM:IAQR:XUBU:6LBJ
 Docker Root Dir: D:\ProgramData\Docker
 Debug Mode: true
  File Descriptors: -1
  Goroutines: 27
  System Time: 2019-08-28T19:20:46.0803711-07:00
  EventsListeners: 1
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: true
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
 Product License: Community Engine

@fernandoespinosa
Copy link
fernandoespinosa commented Sep 12, 2019 •
edited
Loading

TL;DR

I'm on Operating System: Windows 10 Enterprise Version 1803 (OS Build 17134.950) does that mean I'm screwed???

I think my problem is related. I'm running Windows docker in Windows containers mode and any attempts to use --platform=linux go bust:

PS > docker build --platform=linux --network=host --build-arg sample_TAG=7.0 --rm=true .
Sending build context to Docker daemon  2.048kB
Error response from daemon: unsupported os linux

PS > docker pull --platform=linux jetbrains/teamcity-agent
Using default tag: latest
Error response from daemon: unsupported os linux

This is my docker info, as you can see I'm on Operating System: Windows 10 Enterprise Version 1803 (OS Build 17134.950):

PS> docker info
Client:
 Debug Mode: false
 Plugins:
  buildx: Build with BuildKit (Docker Inc., v0.3.0-5-g5b97415-tp-docker)
  app: Docker Application (Docker Inc., v0.8.0)

Server:
 Containers: 4
  Running: 0
  Paused: 0
  Stopped: 4
 Images: 6
 Server Version: 19.03.2
 Storage Driver: windowsfilter
  Windows:
 Logging Driver: json-file
 Plugins:
  Volume: local
  Network: ics l2bridge l2tunnel nat null overlay transparent
  Log: awslogs etwlogs fluentd gcplogs gelf json-file local logentries splunk syslog
 Swarm: inactive
 Default Isolation: hyperv
 Kernel Version: 10.0 17134 (17134.1.amd64fre.rs4_release.180410-1804)
 Operating System: Windows 10 Enterprise Version 1803 (OS Build 17134.950)
 OSType: windows
 Architecture: x86_64
 CPUs: 12
 Total Memory: 15.8GiB
 Name: LTDY7W2X2
 ID: B5V2:ARDA:HGK4:YMNE:XRS3:C675:SPZK:5X7D:GFHC:UWFQ:JB3O:X4KG
 Docker Root Dir: C:\ProgramData\Docker
 Debug Mode: true
  File Descriptors: -1
  Goroutines: 27
  System Time: 2019-09-12T15:59:35.3673461-04:00
  EventsListeners: 1
 HTTP Proxy: http://xxxxx:xxxxx@xxx.xxx.xxx.xxx:xxxx
 HTTPS Proxy: http://xxxxx:xxxxx@xxx.xxx.xxx.xxx:xxxx
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: true
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
 Product License: Community Engine

@cowlinator
Copy link
cowlinator commented Sep 13, 2019 •
edited
Loading

Oh, lcow is supported on Windows RS3 (16299) and above only.

@ebriney
Can you reconfirm that lcow is supported on Windows RS3 (16299) and above, and that docker pull --platform=linux is expected to work on Windows 10 v17134?
If so, this is a bug.

@ebriney
Copy link
Member
ebriney commented Sep 16, 2019

From 19.03:
moby/moby#39108
So if you need LCOW on RS3 we must use older versions (18.09 and older).

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jun 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
lifecycle/locked version/10.0 14393 version/10.0 16299 version/10.0 17134 version/18.03.0-ce-win59
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@fernandoespinosa @mat007 @Mostafa-Armandi @cowlinator @necroTaxonomist @ebriney @chanseokoh @docker-robott
0