-
Notifications
You must be signed in to change notification settings - Fork 11
Conversation
3.x was the only available headers in jessie FIXME: update to buster Signed-off-by: Kibo Hikari <[email protected]>
Signed-off-by: Capuccino <[email protected]>
Signed-off-by: Capuccino <[email protected]>
Signed-off-by: Kibo Hikari <[email protected]>
Signed-off-by: Ayane Satomi <[email protected]>
Signed-off-by: Ayane Satomi <[email protected]>
Signed-off-by: Ayane Satomi <[email protected]>
Signed-off-by: Ayane Satomi <[email protected]>
How do you plan to properly test it on dev machines? |
There's already a way to test ARM images using the QEMU user static Docker images, making my previous strategy obsolete. The point is to consolidate everything into a single codebase, so every environment gets the same result. The old approach is really dirty and I actually hate that version. I have a Raspberry Pi 4 and I've been testing code-server personally so I'm just configuring the CIs to build Docker images for it.
Again we use the same codebase for everything. Where's the lazy in that? You all get the same result as with x86 users.
See comment above. |
I suggest before commenting @SuperSandro2000, analyze the problem we're trying to solve. In a maintainer standpoint, maintaining multiple Dockerfiles per arch is not okay and it leads to deviation. If we can consolidate this into a single codebase, it's easier to track down issues thereon |
I know this. really handy.
If you think this is true. |
Signed-off-by: sr229 <[email protected]>
Any update on this? |
Superseded by #35 |
Travis recently added ARM compile support so we'll use that instead of hacking our way to ARM support.
This will supersede #23