for-mac
runtime
| for-mac | runtime | |
|---|---|---|
| 100 | 4 | |
| 2,449 | 2,095 | |
| 0.4% | - | |
| 3.1 | 8.3 | |
| 11 months ago | over 3 years ago | |
| Go | ||
| - | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
for-mac
- Mac is detecting Docker as a malware and keeping it from starting
- Malware detection prevents Docker Desktop to start on macOS
-
Tell HN: macOS is currently detecting Docker as malware
I just finished porting my projects canonical build process to Docker a few days ago, and had a rude awakening today when MacOS declared Docker malware and deleted its executable. After an hour of trying to figure out why my build was broken, of course.
The workaround is just reinstallation, looks like they had a certificate issue:
https://github.com/docker/for-mac/issues/7520
-
Fixing Docker's Malware Warning on Mac OS Sequoia
The error was reported in issue #7520 of the official Docker for Mac repository. In the thread of this issue, a user named cdcaires shared a set of commands that resolved the problem.
- macOS is detecting Docker as a malware and keeping it from starting
-
🚨 Attention Docker Users on Mac 🚨
For more details, check out the ongoing discussion on GitHub or Docker Community Forum here.
- Caveat for Docker Dev Environment Rug Pull
-
Emacs 29.1 Released
I use containers on Mac and Windows for development (and we deploy on linux). Docker for Mac is _unusably_ slow in my experience. The VM that it runs is a giant resource hog and a battery hog, and doesn't support ipv6 [0] Docker Desktop itself is (another) resource hog, wildly buggy, and painfully slow. It's the epitome of "shitty electron app".
On windows, docker desktop has all of the same issues as it does on mac. Docker's concept of volumes and file permissions on windows are nonsense. Windows updates and Docker Desktop regularly decide to disagree, [1] It's networking support interferes with other applications (like OpenVPN and the Xbox Game Center) [2].
[0] https://github.com/docker/for-mac/issues/1432
[1] https://github.com/docker/for-win/issues/599
[2] https://github.com/docker/for-win/issues/1976
-
Error deploying subgraph on local
version: '3' services: graph-node: image: graphprotocol/graph-node ports: - '8000:8000' - '8001:8001' - '8020:8020' - '8030:8030' - '8040:8040' depends_on: - ipfs - postgres extra_hosts: - host.docker.internal:host-gateway environment: postgres_host: postgres postgres_user: graph-node postgres_pass: let-me-in postgres_db: graph-node ipfs: 'ipfs:5001' matic: 'matic:http://localhost:8545/' GRAPH_LOG: info ipfs: image: ipfs/go-ipfs:v0.10.0 ports: - '5001:5001' volumes: - ./data/ipfs:/data/ipfs postgres: image: postgres ports: - '5432:5432' command: [ "postgres", "-cshared_preload_libraries=pg_stat_statements" ] environment: POSTGRES_USER: graph-node POSTGRES_PASSWORD: let-me-in POSTGRES_DB: graph-node # FIXME: remove this env. var. which we shouldn't need. Introduced by # , maybe as a # workaround for https://github.com/docker/for-mac/issues/6270? PGDATA: "/var/lib/postgresql/data" POSTGRES_INITDB_ARGS: "-E UTF8 --locale=C" volumes: - ./data/postgres:/var/lib/postgresql/data
runtime
-
AER: Error of this Agent is Reported First
Let me give you an example. [Here's one of the best questions I've ever asked on the internet.]https://github.com/kata-containers/runtime/issues/2795) I've seen many better questions asked, but this is the best I've been able to manage. I provided a decent description of the problem, a test-case that allowed other people to reproduce it as well (not relevant in your case), what I tried that didn't work, and the exact log messages and system information that indicated the problem. I then followed up with the people who were helping me and the problem was resolved.
-
Set *minimum* CPU allocation for a service
in parts of prod we use a combination of cgroups (mentioned in the thread already), taskset https://man7.org/linux/man-pages/man1/taskset.1.html, and in other cases (HPC workloads on large clusters) Kata Containers to isolate and optimize application resources: https://katacontainers.io/
-
Docker for Mac M1 RC
It might use a hypervisor though, as the pendulum swings back
https://katacontainers.io/
-
Building a secure/sandboxed environment for executing untrusted code
Kata Containers
What are some alternatives?
UTM - Virtual machines for iOS and macOS
wsl-vpnkit - Provides network connectivity to WSL 2 when blocked by VPN
gvisor - Application Kernel for Containers
amicontained - Container introspection tool. Find out what container runtime is being used as well as features available.
podman - Podman: A tool for managing OCI containers and pods.
singularity - Singularity has been renamed to Apptainer as part of us moving the project to the Linux Foundation. This repo has been persisted as a snapshot right before the changes.
projector-installer - Install, configure and run JetBrains IDEs with Projector Server on Linux or in WSL
kubernetes-goat - Kubernetes Goat is a "Vulnerable by Design" cluster environment to learn and practice Kubernetes security using an interactive hands-on playground 🚀
podman-compose - a script to run docker-compose.yml using podman
microshift - A small form factor OpenShift/Kubernetes optimized for edge computing
valet - A more enjoyable local development experience for Mac.
CDK - 📦 Make security testing of K8s, Docker, and Containerd easier.