We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug Running the Docker image seems to grow out of memory. I'm not sure the --platform=linux/amd64 option has something to do with it.
--platform=linux/amd64
Please note without Docker it works perfectly using the v2.1.0-macOS-ARM64-testnet binary.
v2.1.0-macOS-ARM64-testnet
To Reproduce Steps to reproduce the behavior:
docker run -it \ --platform=linux/amd64 \ --volume /test/full-service/data:/data \ mobilecoin/full-service:v2.1.0-testnet \ --peer=mc://node1.test.mobilecoin.com \ --peer=mc://node2.test.mobilecoin.com \ --tx-source-url=https://s3-us-west-1.amazonaws.com/mobilecoin.chain/node1.test.mobilecoin.com/ \ --tx-source-url=https://s3-us-west-1.amazonaws.com/mobilecoin.chain/node2.test.mobilecoin.com/ \ --chain-id=test
Expected behavior No 137 exit code and no OOMKilled true from docker
Environment (please complete the following information):
2022-11-12 12:22:33.921601878 UTC INFO full-service started: { "GIT_COMMIT": "2ed99e9-modified", "MOBILECOIN_GIT_COMMIT": "42fd014", "PROFILE": "release", "DEBUG": "true", "OPT_LEVEL": "3", "DEBUG_ASSERTIONS": "false", "TARGET_ARCH": "x86_64", "TARGET_OS": "linux", "TARGET_FEATURE": "cmpxchg16b,fxsr,llvm14-builtins-abi,sse,sse2,sse3,sse4.1,ssse3", "RUSTFLAGS": "?", "SGX_MODE": "HW", "IAS_MODE": "PROD" }, mc.app: full-service, mc.module: mc_common::logger::loggers, mc.src: mobilecoin/common/src/logger/loggers/mod.rs:249 Running migration 20202109165203 Running migration 20210303035127 Running migration 20210307192850 Running migration 20210308031049 Running migration 20210325042338 Running migration 20210330021521 Running migration 20210331220723 Running migration 20210403183001 Running migration 20210409050201 Running migration 20210420182449 Running migration 20210625225113 Running migration 20211214005344 Running migration 20220208225206 Running migration 20220215200456 Running migration 20220228190052 Running migration 20220328194805 Running migration 20220427170453 Running migration 20220513170243 Running migration 20220601162825 Running migration 20220613204000 Running migration 20221011050914 Running migration 20221020062248 2022-11-12 12:22:34.423722337 UTC INFO Checking for assigned subaddress proto conversions, mc.app: full-service, mc.module: mc_full_service::db::wallet_db, mc.src: full-service/src/db/wallet_db.rs:213 2022-11-12 12:22:34.425059795 UTC INFO Connected to database., mc.app: full-service, mc.module: full_service, mc.src: full-service/src/bin/main.rs:80 2022-11-12 12:22:34.448389462 UTC ERRO database is locked, mc.app: full-service, mc.module: r2d2, mc.src: /opt/cargo/registry/src/github.com-1ecc6299db9ec823/r2d2-0.8.9/src/lib.rs:121 2022-11-12 12:22:34.449525878 UTC ERRO database is locked, mc.app: full-service, mc.module: r2d2, mc.src: /opt/cargo/registry/src/github.com-1ecc6299db9ec823/r2d2-0.8.9/src/lib.rs:121 2022-11-12 12:23:17.431016968 UTC INFO Ledger DB "/data/ledger.db" does not exist, bootstrapping from peer, this may take a few minutes, mc.app: full-service, mc.module: mc_full_service::config, mc.src: full-service/src/config.rs:327 make: *** [run-full-service] Error 137
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Running the Docker image seems to grow out of memory. I'm not sure the
--platform=linux/amd64
option has something to do with it.Please note without Docker it works perfectly using the
v2.1.0-macOS-ARM64-testnet
binary.To Reproduce
Steps to reproduce the behavior:
Expected behavior
No 137 exit code and no OOMKilled true from docker
Environment (please complete the following information):
Logs
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: