4 ms·

Try Apple's container CLI. I moved a project of mine from colima+docker to it relatively easily, a couple of weekends ago. https://github.com/apple/container h

Try Apple's container CLI. I moved a project of mine from colima+docker to it relatively easily, a couple of weekends ago. https://github.com/apple/container https://github.com/apple/container

yokoprime 5mo ago
Thank you for this, will check it out!
highpost 5mo ago
Here's an example of how to build a simple Alpine Linux container using Apple's containerization CLI. It also demonstrates how to connect to the container through Tailscale SSH using a Tailscale auth key stored in Apple Keychain: https://github.com/highpost/tailscale-macos-container https://github.com/highpost/tailscale-macos-container
- e40 5mo ago
  Why would this be preferred over the Tailscale macOS app? What are the advantages of this method? Thanks.
  - highpost 5mo ago
    The macOS app manages the host Tailscale service, while this example demonstrates how to connect with a *macOS container* using Tailscale SSH based on the Tailscale service under userspace networking mode. This gives the container its own dedicated Tailnet IP and identity without needing to port-forward through the host. edit: For example, I can create a container on my MacBook to run an application. A colleague *in my Tailnet* can then connect to this container to interact with that application from a coffeeshop or airliner while not exposing the rest of my MacBook.
    - e40 5mo ago
      Thanks for the answer. I understand now.
sagarm 5mo ago
Does this project aim for docker cli and api compatibility? Searching for Docker on that page yields no results. Though in their example, they do show an example of a Dockerfile referencing docker.io without shame. Typical Apple behavior, I guess, but grating to see in a OSS tool.
- deleted 5mo ago
  [deleted]
- troad 5mo ago
  This is a weird take, imho. Should they feel shame for using Dockerfiles in their OCI-standard-compliant tool? Would you be happier if they introduced subtly incompatible Applefiles? Why are they obliged to emulate the Docker CLI? This limits them to just shadowing someone else's product. Just use Docker if you want their CLI/API, it uses the same virtualization framework under the hood on Macs.
  - sharts 5mo ago
    Isn’t Containerfile a bit more neutral ground?
copperx 5mo ago
I'm curious to know what kind of project is macOS exclusive?
- troad 5mo ago
  You're surprised that a project by Apple Inc that is basically a wrapper around the Mac virtualisation framework [0] is Mac exclusive? [0] https://developer.apple.com/documentation/virtualization https://developer.apple.com/documentation/virtualization
pram 5mo ago
container is really good, ive been using it to sandbox some CLI tools and it starts up in less than a second
ngai_aku 5mo ago
AFAIK no support for Compose though

Try Apple's container CLI. I moved a project of mine from colima+docker to it relatively easily, a couple of weekends ago. https://github.com/apple/container https://github.com/apple/container

yokoprime 5mo ago

Thank you for this, will check it out!

highpost 5mo ago

Here's an example of how to build a simple Alpine Linux container using Apple's containerization CLI. It also demonstrates how to connect to the container through Tailscale SSH using a Tailscale auth key stored in Apple Keychain: https://github.com/highpost/tailscale-macos-container https://github.com/highpost/tailscale-macos-container

e40 5mo ago
Why would this be preferred over the Tailscale macOS app? What are the advantages of this method? Thanks.
- highpost 5mo ago
  The macOS app manages the host Tailscale service, while this example demonstrates how to connect with a *macOS container* using Tailscale SSH based on the Tailscale service under userspace networking mode. This gives the container its own dedicated Tailnet IP and identity without needing to port-forward through the host. edit: For example, I can create a container on my MacBook to run an application. A colleague *in my Tailnet* can then connect to this container to interact with that application from a coffeeshop or airliner while not exposing the rest of my MacBook.
  - e40 5mo ago
    Thanks for the answer. I understand now.

sagarm 5mo ago

Does this project aim for docker cli and api compatibility? Searching for Docker on that page yields no results. Though in their example, they do show an example of a Dockerfile referencing docker.io without shame. Typical Apple behavior, I guess, but grating to see in a OSS tool.

deleted 5mo ago
[deleted]
troad 5mo ago
This is a weird take, imho. Should they feel shame for using Dockerfiles in their OCI-standard-compliant tool? Would you be happier if they introduced subtly incompatible Applefiles? Why are they obliged to emulate the Docker CLI? This limits them to just shadowing someone else's product. Just use Docker if you want their CLI/API, it uses the same virtualization framework under the hood on Macs.
- sharts 5mo ago
  Isn’t Containerfile a bit more neutral ground?

copperx 5mo ago

I'm curious to know what kind of project is macOS exclusive?

troad 5mo ago
You're surprised that a project by Apple Inc that is basically a wrapper around the Mac virtualisation framework [0] is Mac exclusive? [0] https://developer.apple.com/documentation/virtualization https://developer.apple.com/documentation/virtualization

pram 5mo ago

container is really good, ive been using it to sandbox some CLI tools and it starts up in less than a second

ngai_aku 5mo ago

AFAIK no support for Compose though