2 Dec 2021 |
_hc | I just can't manage anything else, I'm already the blocker on too many things. | 11:57:55 |
proletarius101 | In reply to @eighthave:matrix.org I just can't manage anything else, I'm already the blocker on too many things. i see. take your time~ | 11:58:19 |
_hc | I got pretty far in porting the buildserver to docker: https://gitlab.com/fdroid/fdroidserver/-/merge_requests/1055 | 14:19:14 |
proletarius101 | I propose to add a (gitlab built-in) SAST job into fdroiddata to assist finding Known Vulnerabilities anti-feature: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/10159 | 15:09:47 |
j.r | In reply to @eighthave:matrix.org I got pretty far in porting the buildserver to docker: https://gitlab.com/fdroid/fdroidserver/-/merge_requests/1055 I think for snapshots we could go with docker commit and maybe export the image to a tar file even, but idk if this is what you mean with snapshot | 15:47:31 |
_hc | j.r: docker commit sounds like the right direction. "snapshots" are the terminology for Vagrant/VirtualBox/etc | 15:49:45 |
j.r | Yeah so with docker commit you create/tag an image at the state the container currently is and with docker image save you could export it to a tar file which later could then be imported again.... | 15:51:40 |
_hc | snapshots are used to reset the VM to the clean state before running the build | 15:51:46 |
_hc | j.r: so I guess with Docker we build an "image", the use that image to create a "container" to run each app build, then destroy that container after each build. Sound right? | 15:57:02 |
j.r | In reply to @eighthave:matrix.org j.r: so I guess with Docker we build an "image", the use that image to create a "container" to run each app build, then destroy that container after each build. Sound right? Yeah sounds like the way to go | 15:57:37 |
cde | and then in theory it'd be easy to for anyone to directly use that image
docker run -it --entrypoint /bin/bash name-of-image | 15:58:26 |
cde | Could we publish that image? | 15:58:30 |
_hc | it'll be much too big, like 30 gigs | 15:59:31 |
cde | I have an alias dkcr=docker run -it --entrypoint /bin/bash debian:bullseye locally to quick test things in a fresh container. Like I used it to check if the nss vuln was still exploitable yesterday. | 15:59:35 |
_hc | I do that with vagrant init | 16:00:12 |
jochensp | I recommend podman instead of docker | 16:00:21 |
_hc | well makebuildserver uses vagrant, and vagrant supports docker | 16:01:11 |
_hc | apparently also podman https://www.vagrantup.com/docs/provisioning/podman | 16:01:59 |
jochensp | podman is basically a drop in replacement for the docker command running as a normal user | 16:02:01 |
cde | In reply to @eighthave:matrix.org it'll be much too big, like 30 gigs quick search doesn't seem to find any max sizes for say dockerhub or gitlab container registry.
but even then, it'd still be useful for quicker local testing.
I could never get the existing setup working here locally.
| 16:02:09 |
j.r | I wouldn't like to pull a 30Gig docker image lol.... better build it locally xD | 16:02:45 |
jochensp | yeah, I use mmdebstrap instead of pulling any image | 16:03:25 |
jochensp | (but haven't done that for f-droid yet) | 16:03:45 |
fdroid-meeting-alert-bot | Ping @SylvieLorxu:matrix.org @eighthave:matrix.org @obfusk:matrix.org @uniq:matrix.org Izzy: Weekly meeting at https://meet.calyx.net/fdroid starting | 17:55:34 |
Licaon_Kter[xmpp] | On the road, have fun | 18:00:29 |
cde | you too! | 18:00:50 |
j.r | In reply to @fdroid-meeting-alert-bot:matrix.org Ping @SylvieLorxu:matrix.org @eighthave:matrix.org @obfusk:matrix.org @uniq:matrix.org Izzy: Weekly meeting at https://meet.calyx.net/fdroid starting What is this meeting exactly and who should join it? | 18:16:18 |
cde | we have a weekly developer meeting where we discussing all things fdroid | 18:16:46 |
cde | client, server, data (apps), and more. | 18:16:55 |
Sylvia | Everyone interested in F-Droid is welcome | 18:18:16 |