searx-docker VS Docker-OSX

I'm having the exact same issue on my Arch machine. I think this Github issue might be relevant.

I found a solution so if anyone comes across this thread with the same question here's how I resolved it. I installed Searx using the instructions found here. https://github.com/searx/searx-docker on a laptop and while the instructions got the service up and running the https cert wasn't trusted so I kept getting an error when accessing the service at https://localhost. To resolve the issue I installed Caddy. Trusted the cert, and ran the CA now I can access https://localhost and get Searx without an error. Hopefully someone with more knowledge of web services will comment on this tread and provide a more detailed expiation but here's there commands I ran on my Arch Linux install so modify to your needs. # pacman -S caddy # caddy trust

There is some extra stuff you've got to give it permission to access out of the box. You can see an example csp here https://github.com/searx/searx-docker/blob/4ad61d64991d76a7d300b7b867771ffed9f224ca/Caddyfile#L83 that will work nicely with searx itself however possibly not plugins. Your browsers devtools can be very helpful in figuring out what exactly you need to add/change if something specific is not working. Post the details of that if you are still having issues while using something like what I have linked.

I first attempted to follow the install instructions but got stuck there, and now I have tried to install with docker using searx-docker but have run into an error. Everything was going fine but when I finally try to run with the command:

I just installed a searx instance into my VPS followed the instructions on searx/searx-docker, and i have some question:

If you are not comfortable with Linux you could install Searx using Docker, it's very simple and officially supported: https://github.com/searx/searx-docker

Running macOS legally requires real mac servers and a bespoke storage solution: https://www.datacenterdynamics.com/en/analysis/not-just-stac...

A self-hosted macOS runner will be more economical in the long-run, if you have a spot you can hook it up at, or if you're fine doing things less than legally, you can use https://github.com/sickcodes/Docker-OSX.

Repositório Docker-OSX - Guidelines, troubleshooting, comandos

> What's the licensing situation on this?

1. This project didn't take explicit permission from Apple to redistribute binaries

2. There are multiple jurisdictions where you don't need to explicitly have such permission, it is implied by law

3. Usage of this software implies you already have macOS system. I'm not a lawyer, but it looks to be covered by section 3 of macOS EULA.

4. There are existing precedents of redistribution of macOS binaries for multiple years aready:

- https://github.com/cirruslabs/macos-image-templates/pkgs/con...

- https://hub.docker.com/r/sickcodes/docker-osx

- https://app.vagrantup.com/jhcook/boxes/macos-sierra

And so on.

Google is “friendlier”, because they run some automated scans on the apk and you’re good. Apple has humans run your app to confirm it does what you claim, as well as a battery of automated scans and since they are using the app I’d imagine they look at network traffic as much as possible. I know iOS isn’t shielded from malicious apps, but there’s malware and viruses all over the play store. That’s because it’s free and “friendlier”.

> At Apple things have gotten way worse. Trying to automate release building is practically impossible and will require hours or CI pipeline debugging with error messages that don't mean what they say.

This isn’t Apple’s fault… every build system sucks up a decent amount of time during initial setup. You can cut down massive amounts of time between iterations by adding some common optimizations:

1. Cache artifacts when that step or job succeeds, so if a subsequent step/job fails, you can adjust it and start up where you left off, using the caches artifact to restore the workspace state. This complicates debugging efforts and I personally don’t do any optimization until the pipeline is reliably green each time. I just deal with slow builds and switch to other stuff or work ahead while they run.

2. Fail fast. The CI run should bail out if any critical steps don’t pass, so anything further down doesn’t run for no reason, burning compute time and delaying queued jobs waiting for a runner. While developing the pipeline, watch the logs and when you see something you don’t like, slap the cancel button, or collect a couple things you need to change and iterate with passes with 2-3 changes.

3. Use adequately spec’s hardware. Xcode is resource heavy and compiles need plenty of memory and cpu cores. Play around with what is a good compromise between power and cost. See if your project builds faster with more cpu cores, or faster cpu cores, etc.

> At least Googles process is quite simple and can be dockerized.

One man’s simple is another man’s “practically impossible”. Simple comes from familiarity and confidence. Anyway, you can totally run your builds in docker if you want to, and many do, but I’d personally not introduce more complexity until you have your pipelines running the slow way with the least amount of mental modeling to do. Once you know it all works, then have a go at running the build you know is good, inside a docker container (which in this case is just packing up kvm/qemu/libvirt to facilitate the running of a vm back on the host, but it means you can run mac containers on Linux runners, which will be much cheaper than Mac runners since those are usually Mac hardware)

https://github.com/sickcodes/Docker-OSX

> Also why do I have to pay Apple $125 a year when it costs $100 in the US? The exchange rate from CHF to USD should be in my favor.

Couple theories. 1. They have additional processing or tax expenses when dealing with your currency which they aren’t going to eat the cost of. 2. The higher price could be to deter abuse if for some reason there is an abnormal amount originating from accounts who pay with that currency.

You can use qemu/libvirt/kvm on any Linux host to run macOS pretty easily these days[1]. I run Ventura on unraid with nvidea gpu passthrough and it’s been fairly painless.

You can also run macOS in docker, but it’s ultimately running through qemu/kvm as well[2]

1. https://github.com/kholia/OSX-KVM

2. https://github.com/sickcodes/Docker-OSX

It would be a better idea to setup bluebubbles if you really want imessages while you wait, if you have an old laptop that you can use as a macos server. https://github.com/sickcodes/Docker-OSX is a brilliant solution for macos vm as a docker container. mac hardware not required