Docker setup Issue on arm64 architecture

[a6ar55]

While setting up the docker for kolibri i got some issues while executing "make docker-build-base" later figured out that it was due to the difference in the architecture ,the current one works for only amd64 for some packages(node js and yarn) while mine is arm64.

should i raise an issue or pull request (i made a working base.dockerfile for arm 64) ?

[bjester]

Hi @a6ar55,

Thank you for your interest in contributing.

I think the appropriate fix is to update the dockerfile to instead parameterize amd64 with the result of the following command:

dpkg --print-architecture

That should allow it to work for both amd64 and arm64 host architectures

[a6ar55]

thank you @bjester,

I will proceed with making this change and submitting a pull request. Your assistance is invaluable, and I'm eager in contributing and improving the project.
thanks again.

[a6ar55]

Hey @bjester I updated the "# install nodejs and yarn" and it successfully downloads the packages according to the architecture.

But now I am getting issues with the installation of sqlalchemy which i think is due to the compatibility issue with the python version

I'm reaching out to get your suggestions on resolving this issue. It seems that SQLAlchemy 1.4.49 may not be compatible with Python 2.7.18. I'd appreciate any insights or recommendations you might have to make this work within the Python 2.7 environment itself.

[bjester]

We have a few different dockerfiles, but the base.dockerfile does not seem to be a foundation for any build tooling (e.g. build_whl.dockerfile), so I think we can update it to use python3. Hopefully that will help resolve the issue.

[a6ar55]

okey ,thanks.

[DXCanas]

Just chiming in:

base.dockerfile is actually used in the docker-build-base Make recipe. After being built, it's tagged as learningequality/kolibribase.

learningequality/kolibribase is the tag used for dev.dockerfile and demoserver.dockerfile; search results here.

dev.dockerfile is actually what's used for the Make recipe for docker-devserver:

kolibri/Makefile

Lines 307 to 320 in ef9a11b

	docker-devserver: docker-envlist
	# Build the kolibridev image: contains source code + pip install -e of kolibri
	docker image build \
	-f docker/dev.dockerfile \
	-t "learningequality/kolibridev" .
	docker run --init \
	-v $$PWD/docker/mnt:/docker/mnt \
	-p 8000:8000 \
	-p 3000:3000 \
	--env-file ./docker/env.list \
	"learningequality/kolibridev" \
	yarn run devserver
	echo "Check http://localhost:8000 you should have devserver running there."
	git checkout -- ./docker/env.list # restore env.list file

So @bjester is right that it's not used for build tooling (it seems), but it might be used for the docker dev workflow (which is I guess why you're working on this at all!). The only issues I can potentially foresee are attempting to build a complete Kolibri WHL while in this dev mode; but as it's a Dockerized instance, I don't think that's a common use case.