Differences between Service Fabric on Linux and Windows
There are some features that are supported on Windows but not on Linux. The following differences exist between the latest available releases:
- Envoy (Reverse Proxy) is in preview on Linux
- Standalone installer isn't available on Linux
- Console redirection (not supported in Linux or Windows production clusters)
- The Fault Analysis Service (FAS) on Linux
- Domain Name System (DNS) service for Service Fabric services (DNS service is supported for containers on Linux)
- CLI command equivalents of certain PowerShell commands detailed in PowerShell cmdlets that don't work against a Linux Service Fabric Cluster. Most of these cmdlets only apply to standalone clusters.
- Differences in log implementation that can affect scalability
- Difference in Service Fabric Events Channel
PowerShell cmdlets that don't work against a Linux Service Fabric cluster
- Invoke-ServiceFabricChaosTestScenario
- Invoke-ServiceFabricFailoverTestScenario
- Invoke-ServiceFabricPartitionDataLoss
- Invoke-ServiceFabricPartitionQuorumLoss
- Restart-ServiceFabricPartition
- Start-ServiceFabricNode
- Stop-ServiceFabricNode
- Get-ServiceFabricImageStoreContent
- Get-ServiceFabricChaosReport
- Get-ServiceFabricNodeTransitionProgress
- Get-ServiceFabricPartitionDataLossProgress
- Get-ServiceFabricPartitionQuorumLossProgress
- Get-ServiceFabricPartitionRestartProgress
- Get-ServiceFabricTestCommandStatusList
- Remove-ServiceFabricTestState
- Start-ServiceFabricChaos
- Start-ServiceFabricNodeTransition
- Start-ServiceFabricPartitionDataLoss
- Start-ServiceFabricPartitionQuorumLoss
- Start-ServiceFabricPartitionRestart
- Stop-ServiceFabricChaos
- Stop-ServiceFabricTestCommand
- Get-ServiceFabricNodeConfiguration
- Get-ServiceFabricClusterConfiguration
- Get-ServiceFabricClusterConfigurationUpgradeStatus
- Get-ServiceFabricPackageDebugParameters
- New-ServiceFabricPackageDebugParameter
- New-ServiceFabricPackageSharingPolicy
- Add-ServiceFabricNode
- Copy-ServiceFabricClusterPackage
- Get-ServiceFabricRuntimeSupportedVersion
- Get-ServiceFabricRuntimeUpgradeVersion
- New-ServiceFabricCluster
- New-ServiceFabricNodeConfiguration
- Remove-ServiceFabricCluster
- Remove-ServiceFabricClusterPackage
- Remove-ServiceFabricNodeConfiguration
- Test-ServiceFabricClusterManifest
- Test-ServiceFabricConfiguration
- Update-ServiceFabricNodeConfiguration
- Approve-ServiceFabricRepairTask
- Complete-ServiceFabricRepairTask
- Get-ServiceFabricRepairTask
- Invoke-ServiceFabricDecryptText
- Invoke-ServiceFabricEncryptSecret
- Invoke-ServiceFabricEncryptText
- Invoke-ServiceFabricInfrastructureCommand
- Invoke-ServiceFabricInfrastructureQuery
- Remove-ServiceFabricRepairTask
- Start-ServiceFabricRepairTask
- Stop-ServiceFabricRepairTask
- Update-ServiceFabricRepairTaskHealthPolicy
Next steps
- Prepare your development environment on Linux
- Prepare your development environment on OSX
- Create and deploy your first Service Fabric Java application on Linux using Yeoman
- Create and deploy your first Service Fabric Java application on Linux using Service Fabric Plugin for Eclipse
- Create your first C# application on Linux
- Use the Service Fabric CLI to manage your applications
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for