Repository navigation
Run everything with Docker Compose - #2
Merged
Merged
Conversation
added 2 commits
October 7, 2026 09:36
compose.yaml starts local MongoDB and MySQL from the official images with the root credentials dbclone expects, and a 'dbclone' service (profile cli) built from the new Dockerfile: static binary + docker-cli, talking to the containers over the Docker socket. Profiles persist in a named volume, logs in ./logs. Names, ports and the local password are overridable from the environment.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
compose.yaml: local MongoDB (mongo:7) and MySQL (mysql:8.4) from the official images with the root credentials dbclone expects, plus adbcloneservice (compose profilecli, soup -dnever starts it) built from the newDockerfile.Dockerfile: multi-stage, static binary onalpine+docker-cli. dbclone only needs the Docker CLI and the socket, because every dump/restore still runs inside the two containers.dbclone-configvolume; logs land in./logs. Names, ports and the local root password are overridable (DBCLONE_MONGO_CONTAINER,DBCLONE_MYSQL_CONTAINER,DBCLONE_MONGO_PORT,DBCLONE_MYSQL_PORT,DBCLONE_LOCAL_PASSWORD).Verified
On this machine, with overridden names/ports (the default names and ports were already taken):
Target counts after the clone:
demo.orders5000 documents,demo.users3000 rows, matching the seeded sources. Logs appeared in./logs/<run>on the host.