---
title: "Comment by Mr. Robot on \"Parsing Network Devices Logs with the Elastic Stack\" | Hashnode"
description: "This is good! Just wondering why not use something like: https://hub.docker.com/r/sebp/elk/ ? Any specific reason you went for separate containers?"
url: "https://hashnode.com/posts/parsing-network-devices-logs-with-the-elastic-stack/5e6f7e42bc8844135ba4bf83/comment/5ea574200135fc417662f7d7"
---

[Discussion](https://hashnode.com/posts/parsing-network-devices-logs-with-the-elastic-stack/5e6f7e42bc8844135ba4bf83)

Comment [Parsing Network Devices Logs with the Elastic Stack](https://hashnode.com/posts/parsing-network-devices-logs-with-the-elastic-stack/5e6f7e42bc8844135ba4bf83)

[Mr. Robot](https://hashnode.com/@mrrobot)

[Apr 26, 2020](https://hashnode.com/posts/parsing-network-devices-logs-with-the-elastic-stack/5e6f7e42bc8844135ba4bf83/comment/5ea574200135fc417662f7d7)

This is good! Just wondering why not use something like: [hub.docker.com/r/sebp/elk](https://hub.docker.com/r/sebp/elk/) ? Any specific reason you went for separate containers?

[David Flores (aka: netpanda)](https://hashnode.com/@davidban77)

[Apr 27, 2020](https://hashnode.com/posts/parsing-network-devices-logs-with-the-elastic-stack/5e6f7e42bc8844135ba4bf83/comment/5ea574200135fc417662f7d7#reply-5ea731950135fc417663073d)

It is a really good way try out the ELK stack for sure, but just wanted to show that with the official/default images you are able to build a lab environment to parse virtual devices logs.
