15:51:47 greetings, I'm using a Dockerfile for setting up a few regtest nodes. I face a dns issue inside the container which I can hack my way around but it feels dirty, let me explain. Part of the monerod flag I want to pass is --add-exclusive-node container_name:port . However I dont get where the dns resolution happens, monerod refuses to launch with the various container hostnames I provide, I get a E Exception in 15:51:47 main! Failed to initialize p2p server. So my hack is in the entrypoint script : I have to lookup for the container ip with dig +short container_name and pass that ip in the --add-exclusive-node flag instead and it's working fine. As I said it feels dirty and I thought I could pass hostnames instead of ips for that particular flag, but maybe I'm wrong on that : if you could shed some light that would be great, 15:51:47 thanks in advance 15:52:15 There is no DNS resolution IIRC. 15:52:35 For better err reporting, run with --log-level 1. 15:54:12 gives me this 15:54:13 2022-11-09 15:53:07.618 I Initializing p2p server... 15:54:13 2022-11-09T15:53:07.619462373Z 2022-11-09 15:53:07.619 I Resolving node address: host=monero_buyer_1:28080, port=18080 15:54:13 2022-11-09T15:53:07.619957288Z 2022-11-09 15:53:07.619 E Failed to resolve host name 'monero_buyer_1:28080': Host not found (authoritative):1 15:54:13 2022-11-09T15:53:07.619967670Z 2022-11-09 15:53:07.619 E Failed to parse or resolve address from string: monero_buyer_1:28080 15:54:16 2022-11-09T15:53:07.619974249Z 2022-11-09 15:53:07.619 E Failed to handle command line 15:54:18 2022-11-09T15:53:07.620093305Z 2022-11-09 15:53:07.620 I Deinitializing core... 15:54:28 mmm 15:54:34 think I got it 15:54:53 it's docker compose adding a _1 to the hostname it seems 15:57:16 ha nope sorry my hostname inside the container is monero_buyer_1 and dig +short monero_buyer_1 is successfully getting the ip 16:03:50 ok so given the log, I pass --add-exclusive-node monero_buyer_1:28080 and it seems like it tries Resolving node address: host=monero_buyer_1:28080, port=18080 16:04:47 so the host is the full string and the port is the default port, so I might be using an incorrect syntax for that flag 16:06:37 in essence it seems my issue is that --add-exclusive-node deals fine passing ip:port but treat hostname:port as the host and uses the default port, is there anything I can do on my side ? 16:08:11 Short of adding name resolution, I don't think so. It looks like the lower layer can do since "Failed to resolve host name" suggests it's trying to. 16:08:36 The remaining work would seem to be just command line parsing changes, if that proves correct. 16:09:13 should I open a bug report ? 16:09:27 If you don't want to do it, sure. 16:09:33 If you do, no need. 16:10:10 I'm afraid I'm more into python than c++, will try and see if I can though 16:10:12 "it" being the patch here. 17:13:06 I'm sorry I looked at the code, see where I think it's happening but it's been a while I havnt touched c++ and it would be a mess so I sent a (hopefully) detailed bug report :) 17:13:17 https://github.com/monero-project/monero/issues/8633 17:21:51 Hi! I use a "transfer" RPC method to create tx. How to choose proper "ring_size", "mixin" and "priority"? 17:29:08 Are you going to send old outputs (pre-ringct) ? 17:30:26 If not (likely), you can set all of them to 0. 18:07:43 btc falling. 18:08:46 but, imo, it seems normal, as btc generally falls around this time. i expect it to continue falling until mid 2023. 18:09:32 cvmn: wrong channel 18:10:27 apologies. 18:11:46 #monero-markets :) 22:11:21 "Are you going to send old..." <- I'm not sure what I'm going to send))... (full message at ) 23:04:16 the new wallet rpc docs say " ring_size - unsigned int; Sets ringsize to n (mixin + 1). This field is completely ignored on mainnet." it is optional