Re: Docker experimental multi-arch image build (arm64, i386, amd64)
"John P. Rouillard" <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Norbert: In message <DU2PR01MB8557698E358F8F776984B782E8CEA@DU2PR01MB8557.eurprd01.prod. exchangelabs.com>, SCHLEMMER Norbert writes: >.) docker inspect <image id> > >"Architecture": "arm64", > >"Os": "linux", > >-> seems to be ok > > docker run -it -e SHELL_DEBUG=1 -p 127.0.0.1:8917:8080 --name \ > roundup_demo -v $PWD:/usr/src/app/tracker \ > rounduptracker/roundup-development:multi shell > > > >-> image started, logs below Logs look fine. >Which file are needed at $PWD ? [...] > >+ '[' true '=' false ] > >+ exec /bin/sh Normal startup and you had a shell. So it looks like it's a good image at least. >~ $ ls -lrt > >total 16 > >-rwxr-xr-x 1 root root 291 Jul 19 03:12 roundup_healthcheck > >-rwxr-xr-x 1 root root 5711 Sep 8 02:08 roundup_start > >drwxr-xr-x 2 roundup roundup 4096 Oct 9 14:58 tracker That's exactly what I expected. If the tracker directory is empty, can you cd to that directory and run roundup-demo using demo as the directory. See if it throws any errors. If that works, using the same docker command to run demo rather than shell and see what verbose output reports. Oh one other question, is your userid on the pi 1000? The docker container runs as uid 1000. I would expect it to complain somewhere your could see it, but maybe it just went to the bitbucket on your first failed attempt. Have a great day. -- -- rouilj John Rouillard =========================================================================== My employers don't acknowledge my existence much less my opinions.