Has anyone successfully run UniVerse Personal Edition on an Apple Silicon Mac (Docker + AMD64 emulation)?

SergioV,
 

While I don’t have acess to a Mac, the most common issues on a bare Linux installation are the default kernel parameters for semaphores and message queues. I suggest bumping these by a significant multiplier and trying again.

Regards

JJ

What are your values in uvconfig like SHM_ATT_ADDR  and related to shared memory?

On environments like those as Rosetta memory mappings can get pretty wonky.

Ibrasiskis,

I take the defaults - I’ve never had to change them ina  great many years. The VM host O.S. deals with actual mappings to the physicla O.S. Hosting - or should do so. I thin you should pick this up with the Docker community or support if it seems that type of issue and not simply one of candidates mentioned previously as being too small by default.

Otherwise if someone else here has tried this ona  MAC woth Docker????

Regards

JJ

JJ,

Until there is coredump, I cannot for sure know if it is shared memory. But WSL update was enough to break Shared memory, by changing shared memory space to segmented one, and interleaving heap segments, those invalidating some of memory management heuristics. It was luckily addressed and fixed quickly.

ARM based M series using 64K pages, and 4K pages mixed, with different properties and AOT translation of x86_64 to ARM64 is different beast.
For example even Native Linux with Native software on Apple M has some struggles: 
https://asahilinux.org/docs/sw/broken-software/

Ignas

Ignas,

That almost confirms I think that the issue lies in Docker’s implementation on MAC. I’ve used Docket myself on both Winduws and Linux platforms and had no issues bar one - which was indeed a Docker bug and fixed quickly..

As I don’t have a MAC  to ttry ot myself I think this really needs to go to the Docket community for assistance..

If you really wanted to dig you could look at the failing command in the installation script:

/usr/uv/bin/uv.rc: line 562:  3654 Segmentation fault      $uvbin/init_uvsm $init_uvsm_opt > uvsm.log 2>&1
 and add strace -f to it. This may give you something specific - though be aware the one thing it is guaranteed to get you is a LOT of output. 

Whatever the case, if you get to a closure endpoint on ths I;d love to know the answer.

Regards

JJ

JJ,

I would actually love to spin and hit bpftrace/strace on debug build get to the root cause, or run build I compiled myself.
But I just cannot simply run internal rocket code on my own personal mac laptop :D

You might as well be onto something. On Linux Docker uses namespaces to isolate/remap SYS V shm and semaphores to new container (https://man7.org/linux/man-pages/man7/ipc_namespaces.7.html).  With Apple Virtualisation Framework I am not sure that it emulates and isolates them exactly the same. Docker VMM which as I understand just Linux VM used as root might work better.

Ignas