# CMake Configure OpenSSL Error

**URL:** <https://discourse.slicer.org/t/cmake-configure-openssl-error/6506>\
**Category:** Development\
**Created:** [April 15, 2019, 3:43pm UTC](https://discourse.slicer.org/t/cmake-configure-openssl-error/6506 "2019-04-15T15:43:23Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![marcmclean](https://avatars.discourse-cdn.com/v4/letter/m/7993a0/32.png) [@marcmclean](https://discourse.slicer.org/u/marcmclean)\
**Post date:** [April 16, 2019, 9:13pm UTC](https://discourse.slicer.org/t/cmake-configure-openssl-error/6506/21 "2019-04-16T21:13:58Z")

</div>

Steve, your container is really good. This could be very useful in environments where IT department’s policies make loading software difficult. This simplifies that significantly.

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [April 16, 2019, 9:32pm UTC](https://discourse.slicer.org/t/cmake-configure-openssl-error/6506/22 "2019-04-16T21:32:15Z")

</div>

That is great, we will look into updating the [SlicerDocker](https://github.com/thewtex/SlicerDocker) project so that up-to-date images are published daily.

Note that images used for Continuous integration are already published there daily.

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [April 17, 2019, 2:18pm UTC](https://discourse.slicer.org/t/cmake-configure-openssl-error/6506/23 "2019-04-17T14:18:02Z")

</div>

Yes, having a dockerized version of each nighty build work be great for testing, especially for extensions.

[Previous page](https://discourse.slicer.org/t/cmake-configure-openssl-error/6506.md?page=1)