Sella
Sella
PostsComments
CC#
Created by Sella on 3/23/2024 in #help
Segmentation fault using Debian Bookworm ARM64v8 image during dotnet restore in docker
I'm getting a strange error named "Segmentation fault (core dumped)" when trying to build my dockerfile on the ARM64v8 Bookworm image coming from microsoft dotnet/runtime. this occurs every time on the dotnet restore command while it's not occuring on the AMD64 Bookworm image. Using .NET 8 Some log: 
#11 [build 4/5] RUN dotnet restore --force --no-cache
#11 28.61 Segmentation fault (core dumped)
#11 ERROR: process "/bin/sh -c dotnet restore --force --no-cache" did not complete successfully: exit code: 139

#12 [stage-1  3/16] RUN apt install -y wget apt-transport-https gpg libicu72
#12 CANCELED
------
 > [build 4/5] RUN dotnet restore --force --no-cache:
13.07   Determining projects to restore...
28.61 Segmentation fault (core dumped)
------
Dockerfile:6
--------------------
   4 |     WORKDIR /src
   5 |     COPY ./AzzyBot ./
   6 | >>> RUN dotnet restore --force --no-cache
   7 |     RUN dotnet publish -c Docker -o out
   8 |     
--------------------
ERROR: failed to solve: process "/bin/sh -c dotnet restore --force --no-cache" did not complete successfully: exit code: 139
Error: buildx failed with: ERROR: failed to solve: process "/bin/sh -c dotnet restore --force --no-cache" did not complete successfully: exit code: 139
#11 [build 4/5] RUN dotnet restore --force --no-cache
#11 28.61 Segmentation fault (core dumped)
#11 ERROR: process "/bin/sh -c dotnet restore --force --no-cache" did not complete successfully: exit code: 139

#12 [stage-1  3/16] RUN apt install -y wget apt-transport-https gpg libicu72
#12 CANCELED
------
 > [build 4/5] RUN dotnet restore --force --no-cache:
13.07   Determining projects to restore...
28.61 Segmentation fault (core dumped)
------
Dockerfile:6
--------------------
   4 |     WORKDIR /src
   5 |     COPY ./AzzyBot ./
   6 | >>> RUN dotnet restore --force --no-cache
   7 |     RUN dotnet publish -c Docker -o out
   8 |     
--------------------
ERROR: failed to solve: process "/bin/sh -c dotnet restore --force --no-cache" did not complete successfully: exit code: 139
Error: buildx failed with: ERROR: failed to solve: process "/bin/sh -c dotnet restore --force --no-cache" did not complete successfully: exit code: 139
191 replies
CC#
Created by Sella on 12/8/2023 in #help
SSH Key requirements of Remote Debugger
Can someone explain to me why I can't connect the remote debugger of Visual Studio 2022 with my linux server over SSH? I already tried different types of SSH key formats but it still says to me I need an RSA or DSA key although my keys all have RSA 4096? I also tried the conversion to PEM format via ssh-keygen -p -f <key> -m pem but it's still not accepted and the red fields tell me I have the wrong key type. The key was also converted via PuTTyGen once to the OpenSSH format which doesn't really did something different...
1 replies