dotnet restore fails on mac (core 3 preview 7)

[binish]

dotnet restore fails on macOS ( Sierra 10.12.6)

dotnet new react -au Individual => failes
dotnet restore => fails

dyld: lazy symbol binding failed: Symbol not found: _utimensat
Referenced from: /usr/local/share/dotnet/shared/Microsoft.NETCore.App/3.0.0-preview7-27912-14/System.Native.dylib
Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _utimensat
Referenced from: /usr/local/share/dotnet/shared/Microsoft.NETCore.App/3.0.0-preview7-27912-14/System.Native.dylib
Expected in: /usr/lib/libSystem.B.dylib

[dragfly]

Same problem with preview 8 and macOS Sierra 10.12.5

$ dotnet --version
3.0.100-preview8-013656

$ dotnet build
Microsoft (R) Build Engine version 16.3.0-preview-19377-01+dd8019d9e for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

[...]
You are using a preview version of .NET Core. See: https://aka.ms/dotnet-core-preview
[...]
dyld: lazy symbol binding failed: Symbol not found: _utimensat
Referenced from: /usr/local/share/dotnet/shared/Microsoft.NETCore.App/3.0.0-preview8-28405-07/System.Native.dylib
Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _utimensat
Referenced from: /usr/local/share/dotnet/shared/Microsoft.NETCore.App/3.0.0-preview8-28405-07/System.Native.dylib
Expected in: /usr/lib/libSystem.B.dylib

[dragfly]

Found the solution thanks to https:/dotnet/corefx/issues/39701
Unfortunately .NET Core 3.0 is not supported on Sierra (10.12) as it needs at least 10.13

I guess this issue can be closed

[jchannon]

Found the same for preview9 will try updating my OS

[jchannon]

That did it!

[carlossanlop]

Seems to be resolved. Closing. Feel free to ping us or reopen the issue if you keep seeing problems.

[christianscheuer]

If .NET Core 3.0 needs at least 10.13, shouldn't https://dot.net and https://dotnet.microsoft.com/download be updated so that if you visit those sites on 10.12, you would be redirected to download a version of the SDK that works on these systems?
Or - at least get a more usable error message in the CLI?
I mean, it feels pretty weird that the main web page of the .NET SDK redirects you to download something that doesn't work...