JDBC init scripts travel over the connection, and jdbc:tc URLs can name
one. The form that does not is withCopyFileToContainer, which puts the
file in /docker-entrypoint-initdb.d and lets the postgres entrypoint run
it — and that needs PUT /containers/{id}/archive, the one endpoint the
other two forms never touch.
Werkdock grew it in 0.7.0. This test is what asked for it, and what
corrected it: the first attempt refused path=/, which is precisely what
Testcontainers sends, with the whole path in the tar entry names.
JDBC init scripts travel over the connection, and jdbc:tc URLs can name
one. The form that does not is withCopyFileToContainer, which puts the
file in /docker-entrypoint-initdb.d and lets the postgres entrypoint run
it — and that needs PUT /containers/{id}/archive, the one endpoint the
other two forms never touch.
Werkdock grew it in 0.7.0. This test is what asked for it, and what
corrected it: the first attempt refused path=/, which is precisely what
Testcontainers sends, with the whole path in the tar entry names.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
JDBC init scripts travel over the connection, and jdbc:tc URLs can name
one. The form that does not is withCopyFileToContainer, which puts the
file in /docker-entrypoint-initdb.d and lets the postgres entrypoint run
it — and that needs PUT /containers/{id}/archive, the one endpoint the
other two forms never touch.
Werkdock grew it in 0.7.0. This test is what asked for it, and what
corrected it: the first attempt refused path=/, which is precisely what
Testcontainers sends, with the whole path in the tar entry names.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
mi
manually merged commit b723f56fd7 into main2026-09-11 10:22:32 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
JDBC init scripts travel over the connection, and jdbc:tc URLs can name
one. The form that does not is withCopyFileToContainer, which puts the
file in /docker-entrypoint-initdb.d and lets the postgres entrypoint run
it — and that needs PUT /containers/{id}/archive, the one endpoint the
other two forms never touch.
Werkdock grew it in 0.7.0. This test is what asked for it, and what
corrected it: the first attempt refused path=/, which is precisely what
Testcontainers sends, with the whole path in the tar entry names.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
JDBC init scripts travel over the connection, and jdbc:tc URLs can name one. The form that does not is withCopyFileToContainer, which puts the file in /docker-entrypoint-initdb.d and lets the postgres entrypoint run it — and that needs PUT /containers/{id}/archive, the one endpoint the other two forms never touch. Werkdock grew it in 0.7.0. This test is what asked for it, and what corrected it: the first attempt refused path=/, which is precisely what Testcontainers sends, with the whole path in the tar entry names. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>