Limitations on custom binary running on server

Hi,
What are the rules/limitations on uploading and running binaries in the container as server and in the terminal?
I tried downloading (with wget from the terminal) a Scheme interpreter that I have, but I could not run it from the terminal.
I could not find the answer in TOS.

Did you make sure that you made the binary executable (Using chmod u+x binary)? It should work like it would on any other server.

custom binaries are fine. various considerations:

  • they’re not “supported” in that Glitch doesn’t make it its mission to make these work
  • a few specific kinds of programs are not permitted, regardless of whether they’re custom binaries or not

and on the separate issue of it not working:

  • the operating system in Glitch’s project containers isn’t very recent, so some dependencies might not be right
1 Like

Yes, it was executable already when I extracted it and I chmod it again for good measure.

the operating system in Glitch’s project containers isn’t very recent, so some dependencies might not be right

Ok, you made me realize I was stupid for not checking the linked libraries. I was testing with a Musl binary and musl was not found of course. But the error message tripped me and I jumped to the conclusion that there was something security related enforced by Glitch:

$ /tmp/chicken/bin/csi 
-su: /tmp/chicken/bin/csi: No such file or directory

of course the binary actually exist, but the musl doesn’t

$ ldd /tmp/chicken/bin/csi 
        linux-vdso.so.1 =>  (0x00007ffc5138b000)
        libchicken.so.11 => /tmp/chicken/lib/libchicken.so.11 (0x00007f6b8ca53000)
        libc.musl-x86_64.so.1 => not found
        libc.musl-x86_64.so.1 => not found

I should have though about that earlier.

For the record I tried my glibc build next and unfortunatly the glibc of the glitch container is too old.
It’s ok, I can alway make a new build with older toolchain.

they’re not “supported” in that Glitch doesn’t make it its mission to make these work

That seems very reasonable to me.

a few specific kinds of programs are not permitted, regardless of whether they’re custom binaries or not

Do you mean the things that are detailed in the TOS? I would guess crypto stuff, vpn, spamming tools etc, that’s very reasonable too.

1 Like

ah yeah, you’ll need to build it for Ubuntu 16.04, which has glibc 2.23

yeah, the things in the ToS. Glitch: The friendly community where everyone builds the web actually I looked just now and most of those aren’t listed. spamming and malware are mentioned. you’ll find many other things mentioned outside of the ToS though, but they’re all scattered around help articles and forum posts.

oh one more thing: it might be good to put the source up on your glitch project too, even if you don’t use it there or compile it there. it could help Glitch be able to verify that the program isn’t malicious if they receive reports of abuse from that project.

Ok, thank you for the help :slight_smile:

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.