Re: [Roundup-users] Docker experimental multi-arch image build (arm64, i386, amd64)

[John P. R. <ro...@cs...>]

Hi Norbert:

In message <DU2PR01MB8557BA86651E5B5D42345CFEE8D7A@DU2PR01MB8557.eurprd01.prod.
exchangelabs.com>,
SCHLEMMER Norbert writes:
>Did a test with rounduptracker/roundup:latest under amd64 and with
>mariadb and got it running. Used a docker compose script.
>
>After starting this container the mounted tracker directory will be
>initialised. As a next step I changed config.ini, restarted and the
>mariadb container was connected to the Roundup app. Importing from a
>prev version works too.

Nice. I assume you ran the demo mode first to initialize a tracker,
then stopped the container, changed the config to use a mysql db and
ran init?

Did you try rounduptracker/roundup-development:multi on amd64?
It shoud have support for that arch in it.

If it fails then something may be wrong with the dockerfile or
development Roundup. roundup:latest is supposed to be the 2.3 release,
not the current development (which was used for multi).

If multi amd64 succeeds, then the amd64 build may be broken in some
odd way (e.g. the mariadb/mysql module wasn't available/built). But I
seem to remember from one of your prior emails, that mysql was a db
option.

>But the same docker compose (but
>rounduptracker/roundup-development:multi) doesn't work under arm64,
>the tracker will not be initialised.

When you say will not be initialized, do you mean manually running
roundup-admin init after config.ini changes, or are you using the demo
target?

>For me there should be no difference between amd64 and arm64 during
>the startup procedure

I would agree. Do you see any errors when trying to initialize the
tracker?

Try using the multiarch for amd64 and see if that fails to
initialize.

Thanks.

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.