Open SeaLife opened 1 month ago
I just added privileged: true
to the docker-compose.yml which caused the container to boot up with my code loaded and allowed me to join. As all SYS_CAP* are added on privileged=true, may this error occure due to a specific capability to be missing?
Description of the problem
Hey,
i've recently started programming with the Alt:V SDK in Javascript. I developed everything so far on my local windows computer which works just fine. I tried to run my code today on a linux server (a docker container to be exact) and the server would crash all the time when importing axios or calling fetch(...).
I've created a repository containing a README.md with all the information and the repository contains a reproduction code for the crash.
https://github.com/SeaLife/altv-crash-axios/tree/master
I also tried building a custom image or running the altv-server bare-metal but none of those attempts worked. I also tried the recently pushed RC/DEV version with the newer dotnet and nodejs/v8 version without luck.
I think im just doing something wrong but so far no one could help me solve the issue, so i guess it could be a bug.
Regards SeaLife
Reproduction steps
yarn install
to fetch the dependenciesExpected behaviour
I expect the server to boot up, let me join and get HTTP responses for my requests. (in my case, im doing Discord authentication stuff, which - again - works fine locally on windows)
Additional context
No response
Operating system
Ubuntu 24.04.1 LTS
Version
16.2.13 and 16.2.14-rc
Crashdump ID
No response
Confirmation of issue's presence