# \[Tech Preview\] Storagenode Updater inside Docker

**URL:** <https://forum.storj.io/t/tech-preview-storagenode-updater-inside-docker/17706>\
**Category:** STORJLINGS\
**Created:** [March 16, 2022, 6:13pm UTC](https://forum.storj.io/t/tech-preview-storagenode-updater-inside-docker/17706 "2022-03-16T18:13:46Z")\
**Posts on this page:** 1\
**Showing post:** 32

<div class="post-metadata">

**Author:** ![clement](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/clement/32/11821_2.png) [@clement](https://forum.storj.io/u/clement)\
**Post date:** [March 21, 2022, 12:31pm UTC](https://forum.storj.io/t/tech-preview-storagenode-updater-inside-docker/17706/32 "2022-03-21T12:31:01Z")

</div>

> [@BrightSilence](#):
>
> ```auto
> 2022-03-18 20:08:27,218 CRIT Server 'inet_http_server' running without any HTTP authentication checking
> 
> ```

This is logged at critical level by supervisord because it is assumed as a critical security concern when running supervisord without authentication checks. This is safe to ignore as long as we do not allow HTTP access outside the container; it is configured to only listen to localhost, so it’s reasonable to run without HTTP authentication checks

> <https://github.com/Supervisor/supervisor/issues/694>
>
> This shouldn't be a CRIT level message, it's WARN at most.
> 
> As per the documenta…tion:
> 
> username
> The username required for authentication to this HTTP server.
> 
> Default: No username required.
> 
> Required: No.
> 
> Introduced: 3.0
> 
> If username is not a requirement, a CRIT message should not be generated.

---

_[View the full topic](https://forum.storj.io/t/tech-preview-storagenode-updater-inside-docker/17706)._