# Discourse Assets Missing

**URL:** https://meta.discourse.org/t/discourse-assets-missing/138323
**Category:** Self-hosting
**Tags:** unsupported-install
**Created:** [January 11, 2020, 4:43pm UTC](https://meta.discourse.org/t/discourse-assets-missing/138323 "2020-01-11T16:43:48Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![Remah](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/remah/32/70590_2.png) [@Remah](https://meta.discourse.org/u/Remah)
#### Post date: [January 12, 2020, 9:11pm UTC](https://meta.discourse.org/t/discourse-assets-missing/138323/8 "2020-01-12T21:11:07Z")

</div>

Did you see this topic and this post in particular about podman incompatibility with docker?

> [@Any interest in Podman?](https://meta.discourse.org/t/any-interest-in-podman/118182/20):
>
> I took a shot at this for half an hour or so. Podman is command-compatible but not output-compatible, so launcher gets confused when it tries to parse output. (It’s not hard to tell them apart, docker --version replies with podman version 1.0.5 so this is not a serious impediment.) There is no docker0 network device. The default overlay storage driver in podman is basically the overlay2 implementation and is aliased to it, but the output doesn’t say overlay2 and the output of the docker info c…

---

_[View the full topic](https://meta.discourse.org/t/discourse-assets-missing/138323)._
