I'm noticing that
op is dynamically linked:
$ file op op: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, Go BuildID=6PMb5e52TMhuZNI_2ccD/e0_bUmkGp2msOj5d2-ol/WCzv-nuSBmRQmhzAopOv/9h0_bphpnoZre2vD5JoA, stripped $ ldd op /lib64/ld-linux-x86-64.so.2 (0x7fdd46527000) libpthread.so.0 => /lib64/ld-linux-x86-64.so.2 (0x7fdd46527000) libc.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7fdd46527000)
This isn't necessarily a problem, but when running
op from systems that don't use
glibc (like Alpine Linux, commonly used inside Docker containers), this is a pain.
I know it's written in Go, and so making this a static binary should (in theory!) be possible.
Is there anything stopping the
op tool from being static?
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided