Docker Community Forums

Share and learn in the Docker community.

Why does this forum feel so unmoderated?

Also, am I the only one for whom the huge header on top of this forum is blocking proper navigation?


Now for the required 20 minimum number of characters.

Can you provide an example for the problem?
I usualy click on categories in the burger menu to get back to the categories overview.

Appart from that: I gave up on this forum. It is time to let others perform the artificial ventilation for this forum ^^

1 Like

Ah, it seems no navigation is really missing, as the hamburger menu is all one gets for very wide browser windows too. Also, it may only be a problem when being logged in, in which case the top of my view is partially blocked.

When logged in

When logged in with a smaller window width

When logged out

When logged out with a smaller window width

I love the (non-Windows Server) Docker products, and really appreciate what’s being offered. But not so much love for this forum. Not a problem, there are many more resources.

(Latest Firefox and Chrome on a Mac. Mobile is much better, also for the bullet lists which actually show bullets on mobile but just show some indentation in my desktop browsers.)

The page header dissapears when it’s scrolled out of the screen. When you scroll past the post title, it appears in the bar with the hamburger menu. This bar will become your main navigation menu. Imho, the page header does not provide any value to the forum internal navigation.

I use Docker exclusivly where it is treated as a first class citizen: Linux (Ubuntu/Debian/CentOS).

Yes, that’s actually my main problem, which I did not voice well earlier:

In other Discourse installations, I’m used to always seeing some clickable logo at the top left of the sticky (here: dark blue) header. Even on small width screens. That logo allows me to get to the forum’s home page without the need to go into the hamburger menu. See for example itself.

In this very forum, the Docker logo that links back to is only visible when not having scrolled yet. And that huge header needs one to scroll for sure. :wink:

Just to make sure my screenshots make some sense: it’s the light blue “Welcome to the Docker Community Forums” that confused me, as only a few pixels of that part are ever visible when I’m logged in. I figured that the light blue part would include the navigation that I was looking for (and was mostly hidden by the dark blue part), but logging out confirms it doesn’t.

So, for me, the main “problem” is the sticky navigation not including a direct link to the forum’s overview page.

Aside, maybe the light blue part should not be visible at all when logged in? There is no way to dismiss it otherwise (for me).

Ah, when not logged in, I can dismiss it; the bottom few pixels of the close icon are visible:


But, just in case someone wants to fix it, then I get the navigation or title being partially hidden:

Now I cherish the few light blue pixels that I see when logged in. :slight_smile:

Fully agree the “left over navigation bar” lacks a direct link back to the main page,

I never knew the light blue banner can be dismissed - I tried it and you are right: the navigation items directly undearneath it disapper along with it.

Now we know, the forum does not only lack attention from its moderators, it lacks attention from the ux department as well. What a joy!

1 Like

In other Discourse forums, spam posts like from would not even make until approved. Some setting needs some tweaking here.

First I am only just a user like most others here. I have no moderator or admin rights so I can not make changes here. Sorry if you thought the message implied otherwise.

I do agree that an active admin here would be of benefit.

Just a few seconds ago I was doing my daily check of post at Discourse Meta and noticed that another Beta release notes was posted (14h ago as of this writing) and notified the users of the site I am an admin at with this post.

Also being a Discourse admin at SWI-Prolog site I am very aware that one should pay very close attention to the details in this release concerning the upgrade of the PostgreSQL server from version 12 to 13. When the server was upgraded from 11 to 12 it caused many problems for those that self host.

Sadly :slightly_frowning_face: I am not an admin here so as I can not take the necessary action.

Also @moderators if you could ban this clown, that would be great. They’ve been spamming relentlessly.

This bot comments with GitHub issue text seemingly at random.


I just noticed that the layout issues have been fixed, now also showing a home icon. :+1:

So, someone is still putting some love in the forum? If you need help fighting the spammers and scammers then let us know!

If this site is set to automatically update based on GitHub changes by Discourse then it was Discourse that fixed the issue and not some admin here, so I would not be so quick as to think that there is an active admin.

Maybe the best (and almost funny) example in Exports seems to be a protected word in COPY, where the bot was thinking “word” referred to a question about an Office application on the Docker forums:

Follow these simple steps to do it: Step 1: Open the Microsoft Word document that you want to unprotect and then click on “File” and select “Protect Document” under the section marked “Info”. Step 2: In the drop-down menu, select “Encrypt with Password” and then remove the password from the password field. Click “OK”.

(Possibly copied from here, but the very same guide can be found on other blogs as well. So this may very well be plagiarism of plagiarized content.)

That offer still stands. But even without moderators being assigned: I see quite a few posts being hidden while awaiting moderation, after a few people flagged those posts, like:

It seems a single flag does not suffice, but one or two additional flags probably trigger hiding the post. Not as good as actual removal, but still: flag, please!

1 Like

As I am an admin on other Discourse sites, the number of flags needed is set by the admins


and I believe defaults to 5.

However there is also


which I did not know existed until just now. I don’t even know how a num_spam_flags_to_silence_new_user spam flags is created. Is it a flag that has been approved by an admin? I plan to check on this but not any time soon as it is not of a high importance on the site I admin.

If others want to follow up the site to reach out to the developers of Discourse is

Its sad to see the state of this forum at this point, I think, the only mod/staff I have really seen active here, is @bryceryan which also have provided a lot of help removing spam topic in the past. But also his last active time is a couple of months ago.

But I hope that maybe @justincormack will see this topic and bring some light on the situation, there is for sure a lot of useful information here, and a few people here still keeping it alive.
So I dont hope to see it go in the future.

Maybe just atleast give some of us “veterans” extended permissions


I’ve been in touch with someone at Docker, who wrote May 5th:

Our team has plans to work on the forums once DockerCon has passed.

So, if all is well then things may improve after May 27th. Also, she recommended to reach out to Head of Community, @jawxies, on Slack. I’ve not received a reply to my messages on Slack (May 8th) and here (May 13th) yet, but only a week has passed and surely folks are busy. Fingers crossed?

Hi @avbentem ! Thanks for reaching out and many many thanks for your interest in helping with the forums - I’m really sorry for the late reply. We are knee-deep in DockerCon planning - once our conference is over, I’ll have plenty of time to chat. Please do ping me on Slack. My handle on Slack is @William, not @jawxies.

Many thanks again!



Good news! I talked to @jawxies today and I can now do the much awaited moderation. There’s quite some backlog (but I guess most is about @lewish95 who/which I disabled right away), so I hope to finish cleaning up soon.

moderation backlog

I see a few people (notably @terpz) have been flagging a lot: thanks, and please keep that going. If anyone is trying to reach William Quiviger on Slack, be sure to use @William (the one with the photo), not @William Quiviger.


Finally a silver lining :slight_smile: