Comments (1)
I would agree that removing Darwin support at this time is probably the way to go. We announced the end of Singularity Desktop nearly one year ago now - https://groups.google.com/a/lbl.gov/g/singularity/c/MSsOy6TkkQY/m/vrJWcbkFBQAJ - and the code is likely not in an operational state any more, as it has not received attention since before that time. It just complicates things at present.
To date there hasn't been an indication that it'll be possible to support via community contribution, and the landscape becomes trickier with each new macOS release (tightened security, notarization stuff etc.) as well as the arrival of Apple Silicon.
Most clusters are still AMD64, rather than ARM64. I'd guess this will be true for some time, meaning that a native macOS version of Singularity has less utility over time as people upgrade their machines.
Running Singularity on an M1 mac would be an interesting way to build for ARM clusters in future, but this can be accommodated via a Vagrant based approach once that is supported on these machines somehow.
from singularity.
Related Issues (20)
- OCI ConveyorPacker test failures
- Library ConveyorPacker Test Failure HOT 1
- SIFAssembler test failure
- tmpfs error using singularity with PID namespace on RHEL 8.8 HOT 5
- Does not build an .img file on Vagrant 2.4.1 on Mac(Sonoma 14.5 (23F79)) HOT 2
- 4.1.4 Backports
- Support singularity instance run HOT 2
- Error while building from image: "failed to create symlink /image/rootfs/var/tmp" HOT 11
- oci-mode: fallback to temporary sandbox not working on OCI-SIF images HOT 2
- oci-mode: fallback to tmp-sandbox from docker:// fails with 'no child with platform' error
- e2e: some e2e.Privileged returns not called
- Update manifest / config for correct overlay digest after changes HOT 1
- OCI mode execution fails with relative path to image
- Pull OCI image with overlay, without requiring --keep-layers HOT 1
- Pull OCI image with overlay, with --keep-layers
- Native mode OCI pull only honours platform for Image Indexes
- `overlay seal` is converting root of overlay, not `upper` directory
- `overlay seal` must handle fuse-overlayfs whiteouts sensibly HOT 2
- If fuse-overlayfs is used with a writable overlay, it should always be used in future.
- Join approved network namespaces
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from singularity.