<p>So after some investigations I realized that ZMQ support is not present on the latest tag on the repo (<a href="https://github.com/wouldgo/bitcoind-docker-container/blob/c498879baecc681e0a2ecc5ee5068449782565fc/Dockerfile#L9" rel="nofollow">this</a> line was in charge of giving me the latest tag).</p>

<p>So I think that my problem is by now resolved by using <code>master</code> as building branch.</p>

<p>Thanks at all,
Dario.</p>

CC BY-SA 3.0
2017-04-03T07:39:26.673Z
Note that, latest packages from `ppa:bitcoin/bitcoin` contain ZMQ support
Oleksandr Fediashov
CC BY-SA 3.0
2015-11-27T22:14:05.757Z
2015-11-29T10:27:17.683Z
2015-11-29T10:27:17.683Z
Dario
<p>I'm trying to compile from latest tag the bitcoin repo and in my use case scenario ZeroMQ support would definitely help me.</p>

<p>Reading the documentation I realized <a href="https://github.com/wouldgo/bitcoind-docker-container" rel="nofollow">this</a> rudimental docker container. The Dockerfile installs the <code>libzmq3-dev</code> dependency and I define <a href="https://github.com/wouldgo/bitcoind-docker-container/blob/master/conf/bitcoin.conf#L8" rel="nofollow">these</a> configurations in the <code>bitcoin.conf</code> file.</p>

<p>The result is that inside the container there isn't any bind for the defined mq enpoints and I cannot realize where the error is.</p>

<p>Could someone please help me to enable mq publish mechanism?</p>

<p><em>Update</em>: Now the bitcoin.conf file used is <a href="https://github.com/wouldgo/bitcoind-docker-container/blob/master/conf/bitcoin.conf" rel="nofollow">this</a> running in in debug it logs <a href="http://pastebin.com/LMkgh4j1" rel="nofollow">this</a> debug_log.txt.</p>

CC BY-SA 3.0
2015-11-26T00:42:35.257Z
Your prune line looks weird.
Pieter Wuille
CC BY-SA 3.0
2015-11-26T08:19:27.100Z
@PieterWuille: probably I misunderstood the help line that describes the option. I suppose that the weirdness stands in the angle braket. Am I right?
Dario
CC BY-SA 3.0
2015-11-26T12:43:41.840Z
@PieterWuille I changed the `prune` option with the 1000 value and the log report an incompatibility with the `txindex`. Removing the `prune` at all, I cannot expose the mq enpoints. Is there anything I could do trying to spot the problem?
Dario
CC BY-SA 3.0
2015-11-26T13:05:30.560Z
You cannot enable both txindex and prune. Pick one.
Pieter Wuille
CC BY-SA 3.0
2015-11-26T13:08:21.277Z
infact I've correct removing the prune option. The fact is that there isn't any mq bound on ports specified.
Dario
CC BY-SA 3.0
2015-11-26T13:31:35.637Z
Can you put your debug.log somewhere?
Pieter Wuille
CC BY-SA 3.0
2015-11-26T14:41:12.270Z
Let us [continue this discussion in chat](http://chat.stackexchange.com/rooms/32165/discussion-between-dario-and-pieter-wuille).
Dario
CC BY-SA 3.0
2015-11-27T08:08:48.523Z
@PieterWuille in the chat above I wrote down what you asked for. I'm also there. Thank you very much for your time!
Dario
<bitcoind><zeromq>
Bitcoind with ZeroMQ support
Dario
# Bitcoind with ZeroMQ support

(Asked by: username_0 on 2015-11-26)

I'm trying to compile from latest tag the bitcoin repo and in my use case scenario ZeroMQ support would definitely help me.

Reading the documentation I realized [this](https://github.com/wouldgo/bitcoind-docker-container) rudimental docker container. The Dockerfile installs the `libzmq3-dev` dependency and I define [these](https://github.com/wouldgo/bitcoind-docker-container/blob/master/conf/bitcoin.conf#L8) configurations in the `bitcoin.conf` file.

The result is that inside the container there isn't any bind for the defined mq enpoints and I cannot realize where the error is.

Could someone please help me to enable mq publish mechanism?

*Update*: Now the bitcoin.conf file used is [this](https://github.com/wouldgo/bitcoind-docker-container/blob/master/conf/bitcoin.conf) running in in debug it logs [this](http://pastebin.com/LMkgh4j1) debug\_log.txt.

**Tags:** bitcoind, zeromq

> **Comments:**
> **username_1**: Your prune line looks weird.  
> **username_0**: @username_1: probably I misunderstood the help line that describes the option. I suppose that the weirdness stands in the angle braket. Am I right?  
> **username_0**: @username_1 I changed the `prune` option with the 1000 value and the log report an incompatibility with the `txindex`. Removing the `prune` at all, I cannot expose the mq enpoints. Is there anything I could do trying to spot the problem?  
> **username_1**: You cannot enable both txindex and prune. Pick one.  
> **username_0**: infact I've correct removing the prune option. The fact is that there isn't any mq bound on ports specified.  
> **username_1**: Can you put your debug.log somewhere?  
> **username_0**: Let us [continue this discussion in chat](http://chat.stackexchange.com/rooms/32165/discussion-between-username_0-and-username_1-username_1).  
> **username_0**: @username_1 in the chat above I wrote down what you asked for. I'm also there. Thank you very much for your time!  

---

## 1 answers

### Answer by username_0 on 2015-11-27. Score: 1 | Accepted answer

So after some investigations I realized that ZMQ support is not present on the latest tag on the repo ([this](https://github.com/wouldgo/bitcoind-docker-container/blob/c498879baecc681e0a2ecc5ee5068449782565fc/Dockerfile#L9) line was in charge of giving me the latest tag).

So I think that my problem is by now resolved by using `master` as building branch.

Thanks at all,
username_0.

> **Comments:**
> **username_2**: Note that, latest packages from `ppa:bitcoin/bitcoin` contain ZMQ support  

---

