Skip to content
New issue

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

i can not create docker container #4055

Open
asdaerwrte opened this issue Apr 17, 2024 · 4 comments
Open

i can not create docker container #4055

asdaerwrte opened this issue Apr 17, 2024 · 4 comments
Labels
bug Something isn't working can't reproduce That is unclear how to reproduce the issue

Comments

@asdaerwrte
Copy link

asdaerwrte commented Apr 17, 2024

0: qdrant::startup::setup_panic_hook::{{closure}}
1: <alloc::boxed::Box<F,A> as core::ops::function::Fn>::call
at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/alloc/src/boxed.rs:2021:9
2: std::panicking::rust_panic_with_hook
at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/std/src/panicking.rs:735:13
3: std::panicking::begin_panic_handler::{{closure}}
at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/std/src/panicking.rs:609:13
4: std::sys_common::backtrace::__rust_end_short_backtrace
at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/std/src/sys_common/backtrace.rs:170:18
5: rust_begin_unwind
at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/std/src/panicking.rs:597:5
6: core::panicking::panic_fmt
at /rustc/a28077b28a02b92985b3a3faecf92813155f1ea1/library/core/src/panicking.rs:72:14
7: tokio::runtime::builder::Builder::build
8: qdrant::main
9: std::sys_common::backtrace::__rust_begin_short_backtrace
10: main
11:
12: __libc_start_main
13: _start

Panic occurred in file /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.35.0/src/runtime/scheduler/multi_thread/worker.rs at line 447: OS can't spawn worker thread: Operation not permitted (os error 1)
thread panicked while processing panic. aborting.
./entrypoint.sh: line 25: 7 Aborted (core dumped) ./qdrant $@

Uploading image.png…

@asdaerwrte asdaerwrte added the bug Something isn't working label Apr 17, 2024
@asdaerwrte asdaerwrte changed the title i can not create docker i can not create docker container Apr 17, 2024
@brandonbiggs
Copy link

Looks like it's a permissions issue Operation not permitted . Can you provide additional details on how you're trying to create/run the docker container?

@daopapp
Copy link

daopapp commented Apr 17, 2024

I'm having a similar error on docker stack:

           _                 _
  __ _  __| |_ __ __ _ _ __ | |_
 / _` |/ _` | '__/ _` | '_ \| __|
| (_| | (_| | | | (_| | | | | |_
 \__, |\__,_|_|  \__,_|_| |_|\__|
    |_|

Version: 1.8.4, build: 984f55d6
Access web UI at http://localhost:6333/dashboard

2024-04-17T19:37:34.277004Z  INFO storage::content_manager::consensus::persistent: Loading raft state from ./storage/raft_state.json
2024-04-17T19:37:34.277485Z DEBUG storage::content_manager::consensus::persistent: State: Persistent { state: RaftState { hard_state: HardState { term: 1, vote: 8702183525205197, commit: 6 }, conf_state: ConfState { voters: [8702183525205197], learners: [], voters_outgoing: [], learners_next: [], auto_leave: false } }, latest_snapshot_meta: SnapshotMetadataSer { term: 0, index: 0 }, apply_progress_queue: EntryApplyProgressQueue(Some((7, 6))), peer_address_by_id: RwLock { data: {8702183525205197: http://qdrant_node_0:6335/} }, peer_metadata_by_id: RwLock { data: {} }, this_peer_id: 8702183525205197, path: "./storage/raft_state.json", dirty: false }
2024-04-17T19:37:34.278083Z  INFO storage::content_manager::toc: Loading collection: Vector_index_082ae79b_f534_4e32_b2cc_2abe3c44acb6_Node
2024-04-17T19:37:34.291530Z ERROR qdrant::startup: Panic backtrace:
   0: qdrant::startup::setup_panic_hook::{{closure}}
   1: <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/alloc/src/boxed.rs:2029:9
   2: std::panicking::rust_panic_with_hook
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:783:13
   3: std::panicking::begin_panic_handler::{{closure}}
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:657:13
   4: std::sys_common::backtrace::__rust_end_short_backtrace
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/sys_common/backtrace.rs:171:18
   5: rust_begin_unwind
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:645:5
   6: core::panicking::panic_fmt
             at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/panicking.rs:72:14
   7: collection::shards::shard_holder::ShardHolder::load_shards::{{closure}}.89254
   8: tokio::runtime::runtime::Runtime::block_on
   9: qdrant::main
  10: std::sys_common::backtrace::__rust_begin_short_backtrace
  11: main
  12: <unknown>
  13: __libc_start_main
  14: _start

2024-04-17T19:37:34.291541Z ERROR qdrant::startup: Panic occurred in file /qdrant/lib/collection/src/shards/replica_set/mod.rs at line 261: Failed to load local shard "./storage/collections/Vector_index_082ae79b_f534_4e32_b2cc_2abe3c44acb6_Node/0": Service internal error: Wal error: Can't init WAL: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }
2024-04-17T19:37:34.292025Z DEBUG reqwest::connect: starting new connection: https://telemetry.qdrant.io/

@asdaerwrte
Copy link
Author

Looks like it's a permissions issue Operation not permitted . Can you provide additional details on how you're trying to create/run the docker container?

I am using the creation command from the official website
docker run -p 6333:6333 -p 6334:6334
-v $(pwd)/qdrant_storage:/qdrant/storage:z
qdrant/qdrant

@timvisee
Copy link
Member

@daopapp Is it possible that you're trying to use multiple Qdrant instances on the same directory. That's when you'd typically see this. Each should have their own directory, even if running in a cluster.

@asdaerwrte Is it possible that you're host has limited capabilities (in terms of security), that prevents spawning threads and such?

@generall generall added the can't reproduce That is unclear how to reproduce the issue label Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working can't reproduce That is unclear how to reproduce the issue
Projects
None yet
Development

No branches or pull requests

5 participants