docker build fails outside pipeline due to invalid aleksis meta-package in registry #53
Labels
No labels
Security
TeX
board
done
board
ready
board
todo
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS#53
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When building and deploying the Docker based base setup over at
https://github.com/AlekSIS-org/AlekSIS.git
the process prematurely ends with the following error
Any clue what causes this error. I couldn't find an intuitive solution
moved from AlekSIS-Core#704
@nik any quick idea on a fix here that would allow me to test run this system for a board discussion on school administration software here in the federal state of Saxony-Anhalt tomorrow at 4pm?
Please use the officially released version instead of a development branch.
Also, please do not rely on anything about AlekSIS mirrored to GitHub. The mirror there is only waiting for removal by @hansegucker, we do not endorse or actively maintain the code there.
mentioned in issue #49
@nik Alright, did that. Checked out the tag 2021.12.1 in a separate branch from the original Gitlab at edugit.org but the problem stays exactly the same
@nik it doesnt seem to find the python wheel with "No matching distribution found for aleksis-app-stoelindeling<1.1,>=1.0 (from AlekSIS==2021.12.post0)"
Please post the exact steps you take to run the build.
But, I don't see how we would fix this right now – I assume that for a quick test, there is no need to build the docker image yourself.
AlekSIS-App-Stoelindelingis unreleased, and not a dependency of any released version of the AlekSIS meta-package.Sorry i was unprecise i didn't build i just run 'docker-compose up -d' and this fails with the aforementioned error
FYI @nik the error is replicable with a clean fresh 'docker-compose up -d' on the 2021.12.1 tag of master without further ado
That should by no means build the image locally… It should pull the image from our registry instead, and I did find out why the build fails: Someone has forgotten to bump the version number of the meta distribution to a new
.devversion, so builds with a wrong version number have made it into our development registry. The aleksis-core Dockerfile is using our development registry during the builld (which is not an issue in our CI pipeline, but can cause the errorneous behaviour you are observing if built outside the pipeline).I must admit though that we don't actively test docker-compose, because in all environments we work on we use either venv-based deployments or Kubernetes. If running without Docker is an option for you, please follow the steps in the handbook for installing using pip.
Getting a more or less representetive system before tomorrow seems unlikely though, because you will also need timetable data from somewhere. If you really need that system tomorrow, feel free to contact me privately to arrange paid support. If that is not an option, here are some hints you can follow:
docker pull registry.edugit.org/aleksis/official/aleksisis all that is needed?)changed title from {-Build Process Fails-} to {+docker build fails outside pipeline due to invalid aleksis meta-package in registry+}
assigned to @debdolph
Ah, it seems
docker-compose upreally always builds locally. You need todocker-compose pullmanually to prevent this. (Source:man docker-compose)@debdolph Please clean up the registry – all builds of
aleksiswith a version starting with2021.12.post0published after the respective tag are invalid.Hi @nik no worries and thanks for the help already. Would have been nice to see the system for the discussion tomorrow but honestly we are also in a very early stage of discussion i got the hint to AlekSIS just today through Mike Gabriel (FreieSoftware GmbH) and Daniela Küllertz from the City of Magdeburg. Currently schools in our federal state use anything but Open Source for this purpose but i'll try to debug the issue later on in the discussion and of course if we get a project here we will contribute or involve you. Best and thanks again
mentioned in commit
b275e6d7c0Yep, I already assumed that you came here on this route ;).
In any case, please keep us updated so we can fix the handbook and build process for the next release, if necessary.
@nik no 'docker-compose pull' will only pull the images from for Postgres and Redis. The others are always build locally (if they aren't stored in the local docker space already).
Hmm, strange. But
docker pullon each of them does the trick?Will do if @debdolph is giving me a hint after cleanup i will give it a try again. Sleep well and thanks for the help again @nik
Cleaned up the registry...