[GH-ISSUE #269] How to deploy3FS using docker #165

Closed
opened 2026-10-26 09:46:23 +00:00 by bsakaguchi · 5 comments
Owner

Originally created by @xidiancpy on GitHub (May 7, 2025).
Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/269

Thank you very much to the deepseek team for their work.

  1. I now have a cluster server, but I can't directly deploy 3FS on the host machine. Therefore, I need to use docker to deploy 3FS. Is there any containerized deployment documentation to assist me in completing this deployment?
  2. I can't format the hard disk. I currently have an SSD in mfx format. Can I directly mount it
Originally created by @xidiancpy on GitHub (May 7, 2025). Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/269 Thank you very much to the deepseek team for their work. 1. I now have a cluster server, but I can't directly deploy 3FS on the host machine. Therefore, I need to use docker to deploy 3FS. Is there any containerized deployment documentation to assist me in completing this deployment? 2. I can't format the hard disk. I currently have an SSD in mfx format. Can I directly mount it
Author
Owner
<!-- gh-comment-id:2884374877 --> @Hansyangxingxiang commented on GitHub (May 15, 2025): https://github.com/deepseek-ai/3FS/pull/278/files#diff-ca7e13c458ccb7bf066db5e364787a8420bc72b672d43e5bc881aaeef34b7110
Author
Owner

@huww98 commented on GitHub (May 16, 2025):

You may be interested in our approach to build the image with docker buildx bake, verified by GitHub Action.
And deploy it on Kubernetes with helm chart.

<!-- gh-comment-id:2887444647 --> @huww98 commented on GitHub (May 16, 2025): You may be interested in [our approach](https://github.com/AliyunContainerService/alibabacloud-3FS?tab=readme-ov-file#build-3fs) to build the image with [`docker buildx bake`](https://github.com/AliyunContainerService/alibabacloud-3FS/blob/main/deploy/container/docker-bake.hcl), verified by [GitHub Action](https://github.com/AliyunContainerService/alibabacloud-3FS/actions/runs/15061990434). And deploy it on Kubernetes with [helm chart](https://github.com/AliyunContainerService/alibabacloud-3FS/tree/main/deploy/container/chart).
Author
Owner

@xidiancpy commented on GitHub (May 19, 2025):

https://github.com/deepseek-ai/3FS/pull/278/files#diff-ca7e13c458ccb7bf066db5e364787a8420bc72b672d43e5bc881aaeef34b7110

Thank you very much for your sharing. I encountered a problem when using clickhouse. Could you help me?

When I execute

docker run -d -p 19000:9000 -e CLICKHOUSE_PASSWORD=3fs --name clickhouse-server --ulimit nofile=262144:262144 clickhouse/clickhouse-server:25.3.1.2703

The container reported an error.

/entrypoint.sh: create new user 'default' instead 'default'
Processing configuration file '/etc/clickhouse-server/config.xml'.
Merging configuration file '/etc/clickhouse-server/config.d/docker_related_config.xml'.
Logging trace to /var/log/clickhouse-server/clickhouse-server.log
Logging errors to /var/log/clickhouse-server/clickhouse-server.err.log
Poco::Exception. Code: 1000, e.code() = 0, System exception: cannot start thread, Stack trace (when copying this message, always include the lines below):

  1. Poco::ThreadImpl::startImpl(Poco::SharedPtr<Poco::Runnable, Poco::ReferenceCounter, Poco::ReleasePolicyPoco::Runnable>) @ 0x000000001833d275
  2. Poco::Thread::start(Poco::Runnable&) @ 0x000000001833e1ce
  3. BaseDaemon::initializeTerminationAndSignalProcessing() @ 0x000000000f869b76
  4. BaseDaemon::initialize(Poco::Util::Application&) @ 0x000000000f8652df
  5. DB::Server::initialize(Poco::Util::Application&) @ 0x000000000f7b2b1b
  6. Poco::Util::Application::run() @ 0x00000000183919ba
  7. DB::Server::run() @ 0x000000000f7b2830
  8. mainEntryClickHouseServer(int, char**) @ 0x000000000f7af973
  9. main @ 0x0000000009f61441
  10. ? @ 0x00007fc467505d90
  11. ? @ 0x00007fc467505e40
  12. _start @ 0x0000000006b3502e
    (version 25.3.1.2703 (official build))
<!-- gh-comment-id:2890497648 --> @xidiancpy commented on GitHub (May 19, 2025): > https://github.com/deepseek-ai/3FS/pull/278/files#diff-ca7e13c458ccb7bf066db5e364787a8420bc72b672d43e5bc881aaeef34b7110 Thank you very much for your sharing. I encountered a problem when using clickhouse. Could you help me? When I execute docker run -d -p 19000:9000 -e CLICKHOUSE_PASSWORD=3fs --name clickhouse-server --ulimit nofile=262144:262144 clickhouse/clickhouse-server:25.3.1.2703 The container reported an error. /entrypoint.sh: create new user 'default' instead 'default' Processing configuration file '/etc/clickhouse-server/config.xml'. Merging configuration file '/etc/clickhouse-server/config.d/docker_related_config.xml'. Logging trace to /var/log/clickhouse-server/clickhouse-server.log Logging errors to /var/log/clickhouse-server/clickhouse-server.err.log Poco::Exception. Code: 1000, e.code() = 0, System exception: cannot start thread, Stack trace (when copying this message, always include the lines below): 0. Poco::ThreadImpl::startImpl(Poco::SharedPtr<Poco::Runnable, Poco::ReferenceCounter, Poco::ReleasePolicy<Poco::Runnable>>) @ 0x000000001833d275 1. Poco::Thread::start(Poco::Runnable&) @ 0x000000001833e1ce 2. BaseDaemon::initializeTerminationAndSignalProcessing() @ 0x000000000f869b76 3. BaseDaemon::initialize(Poco::Util::Application&) @ 0x000000000f8652df 4. DB::Server::initialize(Poco::Util::Application&) @ 0x000000000f7b2b1b 5. Poco::Util::Application::run() @ 0x00000000183919ba 6. DB::Server::run() @ 0x000000000f7b2830 7. mainEntryClickHouseServer(int, char**) @ 0x000000000f7af973 8. main @ 0x0000000009f61441 9. ? @ 0x00007fc467505d90 10. ? @ 0x00007fc467505e40 11. _start @ 0x0000000006b3502e (version 25.3.1.2703 (official build))
Author
Owner

@Hansyangxingxiang commented on GitHub (May 20, 2025):

Could you check if there are sufficient CPU and memory resources? My OS is Ubuntu 20.04, and I haven't encountered this issue myself. I referenced the documentation at: https://hub.docker.com/r/clickhouse/clickhouse-serve

docker logs clickhouse-server
/entrypoint.sh: create new user 'default' instead 'default'
Processing configuration file '/etc/clickhouse-server/config.xml'.
Merging configuration file '/etc/clickhouse-server/config.d/docker_related_config.xml'.
Logging trace to /var/log/clickhouse-server/clickhouse-server.log
Logging errors to /var/log/clickhouse-server/clickhouse-server.err.log

clickhouse-client --port 19000 --host 10.10.1.114 --user default --password 3fs
ClickHouse client version 25.3.1.2703 (official build).
Connecting to 10.10.1.114:19000 as user default.
Connected to ClickHouse server version 25.3.1.

c4fea0e6dfc1 :) show databases;

SHOW DATABASES

Query id: 4585d1b6-0588-4c82-8a66-86f1b94e579d

┌─name───────────────┐

  1. │ 3fs │
  2. │ INFORMATION_SCHEMA │
  3. │ default │
  4. │ information_schema │
  5. │ system │
    └────────────────────┘

5 rows in set. Elapsed: 0.002 sec.

c4fea0e6dfc1 :)

<!-- gh-comment-id:2892777042 --> @Hansyangxingxiang commented on GitHub (May 20, 2025): Could you check if there are sufficient CPU and memory resources? My OS is Ubuntu 20.04, and I haven't encountered this issue myself. I referenced the documentation at: [https://hub.docker.com/r/clickhouse/clickhouse-serve](https://hub.docker.com/r/clickhouse/clickhouse-server) docker logs clickhouse-server /entrypoint.sh: create new user 'default' instead 'default' Processing configuration file '/etc/clickhouse-server/config.xml'. Merging configuration file '/etc/clickhouse-server/config.d/docker_related_config.xml'. Logging trace to /var/log/clickhouse-server/clickhouse-server.log Logging errors to /var/log/clickhouse-server/clickhouse-server.err.log clickhouse-client --port 19000 --host 10.10.1.114 --user default --password 3fs ClickHouse client version 25.3.1.2703 (official build). Connecting to 10.10.1.114:19000 as user default. Connected to ClickHouse server version 25.3.1. c4fea0e6dfc1 :) show databases; SHOW DATABASES Query id: 4585d1b6-0588-4c82-8a66-86f1b94e579d ┌─name───────────────┐ 1. │ 3fs │ 2. │ INFORMATION_SCHEMA │ 3. │ default │ 4. │ information_schema │ 5. │ system │ └────────────────────┘ 5 rows in set. Elapsed: 0.002 sec. c4fea0e6dfc1 :)
Author
Owner

@xidiancpy commented on GitHub (May 23, 2025):

Thank you very much for your help. I have solved this problem. Because the server threads were restricted.

<!-- gh-comment-id:2903389472 --> @xidiancpy commented on GitHub (May 23, 2025): Thank you very much for your help. I have solved this problem. Because the server threads were restricted.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/3FS#165
No description provided.