Redirect Docker logs to stdout/stderr and add ant build target#417
Redirect Docker logs to stdout/stderr and add ant build target#417sly4 wants to merge 22 commits intojeffpiazza:masterfrom
Conversation
…ation for a while (10min).
… kiosk dashboard config to reflect slideshow's settings.
* Fix IllegalFormatPrecisionException when passing double to String.format * Fix off-by-10 error in reported times from SuperTimer II
Undo earlier commit that tried to fill in missing decimal point for Super Timer II.
In javascript timer interface, recognize "cease" responses and stop polling.
- Fix timer-in-brower -> timer-in-browser in README.md - Fix GRPM -> GPRM in Advanced Database Set-Up doc
…ents pages. Check for missing photo paths in check-in card renderer.
This fixes URLs when derbynet-server is hosted on one server and served by a different (proxy) server (NGINX).
- Populate sortorder correctly even for the first scene after all deleted. - Repopulate g_all_scenes after assigning a kiosk page, so the in-browser state matches the database. - Confirm before deleting a scene.
to ensure current parameters are reflected correctly.
clear kiosk div when a scene has an unspecified page for a kiosk.
|
Could you please rebase to current mainline? This seems to have been branched a while ago. From what I can tell, just 6c290b0 and c54afd3 are the intended changes. I'm not at all deep on docker, but I'm wondering if there shouldn't be some provision for building with --platform options and maybe others. Also, I'm still not 100% clear whether 'docker build' or 'docker buildx build' is the preferred expression. |
|
Given that DerbyNet is used on both AMD64 and ARM64 platforms I would also recommend leveraging the docker buildx build with a --platform option to properly support the multi-arch builds. Recommendation: Add a configurable docker.platform property — like the other properties at the top of the file, defaulting to something sensible: There is also a difference between the docker-deps vs the dist.debian dependency chain: |
|
Hi Jeff and James,
I will rebase the PR to the current mainline; I apologize for the oversight.
I will also look into the questions regarding the Docker build
process—specifically the platform options and the dependency differences
noted—and attempt to address them in the next update.
Thank you,
John
…On Mon, Feb 16, 2026, 15:21 James Ford ***@***.***> wrote:
*jamestford* left a comment (jeffpiazza/derbynet#417)
<#417 (comment)>
Given that DerbyNet is used on both AMD64 and ARM64 platforms I would also
recommend leveraging the docker buildx build with a --platform option to
properly support the multi-arch builds.
Recommendation: Add a configurable docker.platform property — like the
other properties at the top of the file, defaulting to something sensible:
There is also a difference between the docker-deps vs the dist.debian
dependency chain:
Looking at the dependency chains:
docker-deps depends on: generated, timer-in-browser
dist.debian depends on: generated, timer-jar, timer-in-browser, docs-dist
So docker-deps is missing timer-jar and docs-dist compared to the Debian
package. So the timer jar and full docs are built for the Debian package
but never make it into the Docker image because the Dockerfile doesn't copy
them.
—
Reply to this email directly, view it on GitHub
<#417 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AECI22MGLT5I3IR27AJJA6L4MIRFXAVCNFSM6AAAAACVGWPNVSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSMJQGM3TSOBSGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
5 participants
This PR updates the Docker configuration to adhere to container logging best practices and simplifies the build process.