dolthub / doltlab-issues

Issue tracking for DoltLab
MIT License
5 stars 2 forks source link

cannot run doltlab on mac / arm #67

Open chicco785 opened 1 year ago

chicco785 commented 1 year ago

I am trying to test doltlab on my dev environment (a Mac Book Pro M2), but it looks like binaries work only on amd64 architecture:

 % ./start-doltlab.sh 
Setting DEFAULT_USER=admin
Setting DEFAULT_USER_PASSWORD=DoltLab1234
Setting DEFAULT_EMAIL=no-reply@zaphiro.ch
Setting EMAIL_CLIENT_HOSTNAME=localhost
6ca7aa7af9066d6bf452fff78aeb77e7f67ecbe921735d7c1561d5d7947cb09e
./start-doltlab.sh: line 57: ./gentokenenckey: cannot execute binary file
chicco785 commented 1 year ago

To complement, the test was executed on ubuntu vm inside the mac.

chicco785 commented 1 year ago

I have been able to install it using https://lima-vm.io/

chicco785 commented 1 year ago

the scripts works... but the database image start fails, i will try to run more tests

chicco785 commented 1 year ago

it turns out that once generated key files and envoy template, I am able to run dolt lab natively on mac without issues (i.e. outside of a vm... on lima using qemu for simulating x86, db image still fails)

coffeegoddd commented 1 year ago

@chicco785 very cool that you were able to run DoltLab on an M2 without a VM! Currently we only officially support/build for Linux x86, but if we see more requests for additional architectures/environments, this could change.

chicco785 commented 1 year ago

@chicco785 very cool that you were able to run DoltLab on an M2 without a VM! Currently we only officially support/build for Linux x86, but if we see more requests for additional architectures/environments, this could change.

still what puzzle me, is that it fails on VM with QEMU, but that's surely not related to you.

considering that the best machines now on AWS are AWS Graviton3 based on ARM, I think it won't be a bad idea. Also, in most of the cases (at least for docker and go-lang) multi platform builds are really easy peasy.

orefalo commented 1 year ago

Since the application is built in go, it should be no issues releasing an arm binary. it would make first approach so much smoother.