-
Notifications
You must be signed in to change notification settings - Fork 36
/
index.html.md.erb
105 lines (59 loc) · 4.13 KB
/
index.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
---
title: TAS for VMs [Windows] overview
owner: Windows
---
<%= vars.windows_runtime_full %> help you provision, operate, and manage Windows stemcells
on <%= vars.platform_name %>.
After you install the <%= vars.windows_runtime_abbr %> tile on the VMware Tanzu Operations Manager Installation Dashboard,
developers can push .NET apps to Windows Diego Cells using the [Cloud Foundry Command Line Interface](../cf-cli/index.html) (cf CLI).
For the <%= vars.windows_runtime_abbr %> release notes,
see [<%= vars.windows_runtime_full %> <%= vars.v_major_version %>
Release Notes](release-notes.html).
## <a id='reqs'></a> Requirements
To install the <%= vars.windows_runtime_abbr %> tile, you must have:
* Tanzu Operations Manager 3.0 and <%= vars.app_runtime_full %> <%= vars.v_major_version %> deployed to vSphere, Amazon Web Services (AWS), Google Cloud Platform (GCP), or Azure.
* A Windows stemcell. For information about obtaining or creating a Windows stemcell, see [Downloading or creating Windows stemcells](./stemcells.html).
The minimum resource requirements for each Windows Diego Cell are:
* Disk size: 64 GB (100 GB recommended)
* Memory: 16 GB
* CPUs: 4
## <a id='contents'></a>Contents
### <a id='understand'></a> About <%= vars.windows_runtime_abbr %>
* [Product architecture](architecture.html)
### <a id='install'></a> Installation guide
* [Downloading or creating Windows stemcells](stemcells.html).
* [Creating a Windows stemcell for vSphere using stembuild](create-vsphere-stemcell-automatically.html).
* [Installing and configuring <%= vars.windows_runtime_abbr %>](installing.html).
* [Windows Diego Cells in isolation segments](isolation.html).
* [Migrating apps to <%= vars.windows_runtime_abbr %>](migrating.html).
### <a id='admin'></a> Admin guide
* [Upgrading <%= vars.windows_runtime_abbr %> and Windows stemcells](./upgrade-windows.html).
* [Troubleshooting Windows Diego Cells](./troubleshooting.html).
### <a id='dev'></a> Developer guide
* [Deploying .NET apps](develop.html).
* [Using SMB volumes in .NET apps](smb-volumes-apps.html).
* [Changing Windows Stacks](../devguide/deploy-apps/windows-stacks.html).
* [Tips for .NET developers](using.html).
## <a id='limitations'></a> Limitations
Here are the limitations that affect Windows containers in <%= vars.windows_runtime_abbr %>:
* [Windows Server container limitations](#limitations-windows)
* [<%= vars.windows_runtime_abbr %> limitations](#limitations-tasw)
### <a id='limitations-windows'></a> Windows server container limitations
Windows Server Core Containers are used in <%= vars.windows_runtime_abbr %>.
These are known Windows Server container limitations:
* Windows Server Core containers support the host VM's time zone only.
In <%= vars.windows_runtime_abbr %>, the host and container time zone is always UTC.
* Windows Server 2019 Core images support only Lucida Console font.
No other fonts are supported, and no others can be installed.
### <a id='limitations-tasw'></a> <%= vars.windows_runtime_abbr %> limitations
<%= vars.windows_runtime_abbr %> has the following limitations:
* <%= vars.windows_runtime_abbr %> can be installed in an environment with the NSX Container Plugin (NCP), but NCP cannot be used with Windows containers in <%= vars.windows_runtime_abbr %>. For more information about NCP, see [What's New](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/2.5/rn/NSX-Container-Plugin-25-Release-Notes.html#about) in the VMware documentation.
* Developers cannot push Docker or other OCI-compatible images to Windows Diego Cells.
* Container-to-container networking is not available for Windows-hosted apps.
* OpenStack is not supported for <%= vars.windows_runtime_abbr %>.
Contact your VMware representative for information about OpenStack deployments.
* SMB is supported, but Volume Services is not supported.
* Due to Known Issue #244 in Windows Server OS, apps hosted on <%= vars.windows_runtime_abbr %> cannot
route traffic when deployed with the IPsec.
For more information, see [Traffic to containers via NAT stops working when using IPsec
to encrypt network connections](https://github.com/Microsoft/hcsshim/issues/244) on GitHub.