OpenSlides - digital motion and assembly system

[girish]

@jimcavoli I tried building it again the other day and still got the same error. So, I have to investigate why. Maybe something with multi-state builds and our build server.

Step 1/33 : FROM cloudron/base:2.0.0 AS base
 ---> afa4cfc125b4
Step 2/33 : ARG OPENSLIDES_VERSION=3.3
 ---> Using cache
 ---> ab03eb3a365d
Step 3/33 : ARG NODE_VERSION=13.14.0
 ---> Using cache
 ---> fb11ecf942b5
Step 4/33 : RUN apt-get update &&     apt-get -y install       apt-transport-https       bzip2       curl       g++       gcc       git       gnupg2       libpq-dev       make       postgresql-client       rsync       wait-for-it       wget       xz-utils       zlib1g-dev       libffi-dev       dnsutils       iputils-ping       netcat       procps       traceroute       libxml2-dev       libxmlsec1-dev       libxmlsec1-openssl       pkg-config       python3-setuptools       gunicorn3     &&     rm -rf /var/cache/apt /var/lib/apt/lists
 ---> Using cache
 ---> 74dcae334cc2
Step 5/33 : FROM base as build
 ---> 74dcae334cc2
Step 6/33 : RUN mkdir -p /app/{src,build} &&     curl -L https://github.com/OpenSlides/OpenSlides/archive/${OPENSLIDES_VERSION}.tar.gz | tar zxf - --strip-components 1 -C /app/src &&     chown -R cloudron:cloudron /app/src
 ---> Running in e115acee95fb
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100     9  100     9    0     0     84      0 --:--:-- --:--:-- --:--:--    85

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
The command '/bin/bash -c mkdir -p /app/{src,build} &&     curl -L https://github.com/OpenSlides/OpenSlides/archive/${OPENSLIDES_VERSION}.tar.gz | tar zxf - --strip-components 1 -C /app/src &&     chown -R cloudron:cloudron /app/src' returned a non-zero code: 2
Failed to build app. See log output above.

[girish]

@jimcavoli Do you mind if I make it a single stage Dockerfile like the other apps?

edit: Actually, that seems easy since you have already written in to branch off the base nicely.

[jimcavoli]

@girish I could try to adjust it to be a straight-through Dockerfile. Alternately, if you aren't running with DOCKER_BUILDKIT=1 on that machine (which it appears not to be based on output), would you want to give that a shot? As of Docker 20.10.0 (released 8 December 2020), it is considered a stable core feature.

I've got other packagings coming soon that are written to use the same build features, especially when there's a lot of things to build/download, so it'd be nice to know where we're going to land on this. Looks like packages on both my 18.04 and 20.04 boxes are at 19.03.8 which is the 10 March 2020 release. I do happen to be running 20.10.2 on my development machine (and the remote Ubuntu 20.04 build server to be technical, which is the latest, 04 January 2021 release), but it's not like the artifacts are any less compatible after being output with recent versions (those containers ship just fine onto my test Cloudron).

It seems to me like the buildkit engine should be preferable and backward-compatible as described in https://docs.docker.com/develop/develop-images/build_enhancements/ certainly in the 20.x series and beyond, but I've had no issues using it full-time for over a year on the 19.x series and mixing 20.x builds to 19.x runtimes as well.

[girish]

@jimcavoli Yes, I can fix it up. I actually use our build service app which doesn't have BUILDKIT set (assuming, it's off by default). Currently, all cloudrons and all our related services are around Docker 19. I guess we should upgrade Docker to 20 in the next Cloudron release which will help us move forward with the buildkit stuff.

[jimcavoli]

@girish Sounds good; let me know if you need anything along the way - happy to help in any way I can!

[bubonicfred]

@jimcavoli any progress on this, have to run a small conference in a month.

[girish]

@bubonicfred I was just looking into this today. @jimcavoli has finished up the packaging as such.

@jimcavoli where did you find the packaging instructions/docs from? I was trying to just follow through the Dockerfile but it seems quite complicated and I could not find any instructions or code on the openslides site atleast

[jdaviescoates]

@girish said in OpenSlides - digital motion and assembly system:

I was trying to just follow through the Dockerfile but it seems quite complicated and I could not find any instructions or code on the openslides site atleast

Is one of these what you're looking for?

https://github.com/OpenSlides/openslides-docker-compose
https://github.com/OpenSlides/OpenSlides/tree/master/docker
https://github.com/OpenSlides/OpenSlides/blob/master/README.rst#setup-docker-images

[jimcavoli]

@girish Yeah, what @jdaviescoates posted is the thing - it's largely not documented all that well from the technical setup perspective. I just sort of...figured it out? There's not that many components and it's a pretty standard python app. Because it's not well-documented on the project's part insofar as running is concerned, that's a large part of why I made the readme and put all the notes in that I did.

[girish]

@jimcavoli Oh, I completely missed your notes in the README ! I will take a look again.

[jimcavoli]

I've updated https://git.cloudron.io/jimcavoli/openslides-app with the latest changes for version 3.3 of Openslides. Dockerfile is still multi-staged for the time being. @girish do you want to take another pass at building as-is or should I work on making the Dockerfile straight through.

[girish]

@jimcavoli I think Dockerfile straight would be great. How much work do you think it is? Maybe you can quickly try hacking away and see if it's not too much work?

[jimcavoli]

@girish So the gzip failure is independent the staged builds. Arguing with tar/gzip and GitHub about file formats presently, but I can replicate the issue you were having and am testing against the same Dockerfile with and without buildit on, so once I get that sorted, we can regroup and go from there.

[hollosch]

@jimcavoli said in OpenSlides - digital motion and assembly system:

I've updated https://git.cloudron.io/jimcavoli/openslides-app with the latest changes for version 3.3 of Openslides. Dockerfile is still multi-staged for the time being. @girish do you want to take another pass at building as-is or should I work on making the Dockerfile straight through.

Hi, Openslides isn't actually in the cloudron-appstore - is it broken?

[jimcavoli]

@hollosch No, work remains "in progress" for the time being to get a reliable package finished before it heads there. You can keep track by the "WIP" tag on the thread right now - it'll go "Solved" and green once completed

[Benoit]

Hi @girish do you think Openslides can work on Cloudron ? Any news about it ?

[girish]

@Benoit have to investigate, it's quite a complex app to package ! See https://github.com/OpenSlides/OpenSlides#development . Last, I checked, there were no clear instructions for installations from source, so one has to reverse engineer from their docker files.

[jimcavoli]

@girish I’m still around - I can pick this back up in the next week or two

[micmc]

@jimcavoli said in OpenSlides - digital motion and assembly system:

@girish I’m still around - I can pick this back up in the next week or two

Be my guest!

[girish]

@jimcavoli yes, please I will be happy to get this integrated. I think I have addressed the platform issues in the releases since.