Implement Orbstack compatibility with acelink (almost working)

[ghost]

Given that Orbstack (docker Mac alternative) is lighter and less-consumer than docker, I've been trying it, and it works awesome too.

The only problem that I've found is that Acelink is not able to find Orbstack id (or whatever is named), so that turns into you being required to manually open Orbstack before (once you manually open it, it behaves like docker, creating the container and opening VLC,IINA...)

It would be awesome if you modify Acelink to auto-open Orbstack too!!

Thanks in advance.

[florius0]

How did U set it up with orbstack? I use OrbStack v1.0.0 and acelink is trying to connect to different docker unix socket, not the one created by OrbStack

[ghost]

How did U set it up with orbstack? I use OrbStack v1.0.0 and acelink is trying to connect to different docker unix socket, not the one created by OrbStack

I installed OrbStack, changed the context through terminal and ensure that every time I want to use ace link orbstack is open.

Additionally, I made an alias on .zshrc to to always open OrbStack with its command line command 'orb':

alias docker='orb; docker'

Also opened an issue on OrbStack GitHub repository about the problems with the context changes, but the owner wasn't that much helpful.

Issue referred here

Maybe this results helpful to @blaise-io.

[blaise-io]

I won't support Orbstack unless it has a drop in replacement of the Docker CLI, otherwise there's double work and a lot of gotchas, because Ace Link heavily interacts with the docker cli.

You might be best off just using the blaiseio/acelink Docker image and opening streams manually or using a small shell script accepting an Acestream hash. Ace Link is in its core just starting a Docker container with an AceStream server and then launching a VLC with <acestream server>/<hash>.

[florius0]

it has a drop in replacement of the Docker

It does, the only issue with acelink is that it does not detect docker contexts properly as described in #77

[blaise-io]

Oh that's good! Can you give me your output of these commands?

1 docker context inspect --format '{{.Endpoints.docker.Host}}'
2 docker context inspect
3 docker context ls

[Ki1L3r]

1. for command 1 you need to spicify the name : For example

podman context inspect podman-machine --format '{{.URI}}'
ssh://[email protected]:51409/run/user/501/podman/podman.sock

2. podman context inspect:

podman context inspect                                      
[]

3. podman context ls

podman context ls                                           
Name                         URI                                                         Identity                                     Default
podman-machine               ssh://[email protected]:51409/run/user/501/podman/podman.sock  /Users/x/.ssh/podman-machine          false
podman-machine-default       ssh://[email protected]:49665/run/user/501/podman/podman.sock  /Users/x/.ssh/podman-machine-default  false
podman-machine-default-root  ssh://[email protected]:49665/run/podman/podman.sock           /Users/x/.ssh/podman-machine-default  false
podman-machine-root          ssh://[email protected]:51409/run/podman/podman.sock           /Users/x/.ssh/podman-machine          true

➜ ~

[blaise-io]

I'm not planning to support this in the short term. For now, you could use the server without the UI, maybe add some wrapping to easily launch streams.

[Ki1L3r]

it would be nice at least to have the wrapper and manually run the server if possible

Thanks a lot

[blaise-io]

https://github.com/n3d1117/acestream-iina someone created one here, but you'd have to adjust a few commands from docker to podman.