AppFlowy-IO/AppFlowy

Fork 0

mirror of https://github.com/AppFlowy-IO/AppFlowy.git synced 2026-03-24 12:56:59 +00:00

[GH-ISSUE #389] [Bug] Docker Hub (app_flowy:1): Gtk-WARNING **: 10:44:25.079: cannot open display: #179

New issue

Closed

opened 2026-03-23 20:33:27 +00:00 by mirror · 8 comments

mirror commented

2026-03-23 20:33:27 +00:00

Owner

Originally created by @tw0b33rs on GitHub (Feb 26, 2022).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/389

When using the instructions provided at https://appflowy.gitbook.io/docs/essential-documentation/install-appflowy/installation-methods/installing-with-docker with the container from Docker Hub I receive the following error:

(app_flowy:1): Gtk-WARNING **: 10:44:25.079: cannot open display:

System information:
MacBook Air (Retina, 13-inch, 2018)

Is anything missing here?

Thank you!

Originally created by @tw0b33rs on GitHub (Feb 26, 2022). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/389 When using the instructions provided at https://appflowy.gitbook.io/docs/essential-documentation/install-appflowy/installation-methods/installing-with-docker with the container from Docker Hub I receive the following error: (app_flowy:1): Gtk-WARNING **: 10:44:25.079: cannot open display: System information: MacBook Air (Retina, 13-inch, 2018) Is anything missing here? Thank you!

mirror closed this issue

2026-03-23 20:33:27 +00:00

mirror commented

2026-03-23 20:33:28 +00:00

Author

Owner

@bolshoytoster commented on GitHub (Feb 26, 2022):

@tenneck note the text on the page you linked:

Note: Appflowy inside docker needs access to your X server. In case of lack of permissions, it's recommended to build the docker image yourself. The least recommended option is running xhost + before running the container, but this command is ! So make sure you run xhost - after it.

You might need to run xhost + on your host to give permission to the for the docker process to access it.

Make sure to run xhost - afterwards otherwise anyone on your network would be able to connect.

@bolshoytoster commented on GitHub (Feb 26, 2022): @tenneck note the text on the page you linked: > Note: Appflowy inside docker needs access to your X server. In case of lack of permissions, it's recommended to build the docker image yourself. The least recommended option is running xhost + before running the container, but this command is ! So make sure you run xhost - after it. You might need to run `xhost +` on your host to give permission to the for the docker process to access it. Make sure to run `xhost -` afterwards otherwise anyone on your network would be able to connect.

mirror commented

2026-03-23 20:33:28 +00:00

Author

Owner

@Ab19a1l commented on GitHub (Mar 25, 2022):

Same problem is happening, but I am building on VM, do i need to do anything else to set it up?

@Ab19a1l commented on GitHub (Mar 25, 2022): Same problem is happening, but I am building on VM, do i need to do anything else to set it up?

mirror commented

2026-03-23 20:33:29 +00:00

Author

Owner

@Loocos commented on GitHub (Mar 27, 2022):

@tenneck note the text on the page you linked:

Note: Appflowy inside docker needs access to your X server. In case of lack of permissions, it's recommended to build the docker image yourself. The least recommended option is running xhost + before running the container, but this command is ! So make sure you run xhost - after it.

You might need to run xhost + on your host to give permission to the for the docker process to access it.

Make sure to run xhost - afterwards otherwise anyone on your network would be able to connect.

In my case, I'm getting the same message "xhost: unable to open display """ when I type xhost +
I'm not familiar with this and made search in order to understand what's going on and what I'm doing wrong but I still don't know why.

@bolshoytoster Could I ask you why it's needed and blocking ? I would want to use it as a web app only.

Help would be really appreciated

Thanks in advance for your anwsers.

@Loocos commented on GitHub (Mar 27, 2022): > @tenneck note the text on the page you linked: > > > Note: Appflowy inside docker needs access to your X server. In case of lack of permissions, it's recommended to build the docker image yourself. The least recommended option is running xhost + before running the container, but this command is ! So make sure you run xhost - after it. > > You might need to run `xhost +` on your host to give permission to the for the docker process to access it. > > Make sure to run `xhost -` afterwards otherwise anyone on your network would be able to connect. In my case, I'm getting the same message "xhost: unable to open display """ when I type `xhost +` I'm not familiar with this and made search in order to understand what's going on and what I'm doing wrong but I still don't know why. @bolshoytoster Could I ask you why it's needed and blocking ? I would want to use it as a web app only. Help would be really appreciated Thanks in advance for your anwsers.

mirror commented

2026-03-23 20:33:29 +00:00

Author

Owner

@bolshoytoster commented on GitHub (Mar 27, 2022):

@Loocos could you try running appflowy with DISPLAY=:0?

So like DISPLAY=:0 docker run ...

@bolshoytoster commented on GitHub (Mar 27, 2022): @Loocos could you try running appflowy with `DISPLAY=:0`? So like `DISPLAY=:0 docker run ...`

mirror commented

2026-03-23 20:33:29 +00:00

Author

Owner

@Loocos commented on GitHub (Mar 27, 2022):

@Loocos could you try running appflowy with DISPLAY=:0?

So like DISPLAY=:0 docker run ...

Still same, I've tried everything. But I think I got the anwser by joining the discord, I found this issue : https://github.com/AppFlowy-IO/AppFlowy/issues/313
And that's what I'm trying to do. I want to host it and use it on my domain. But it's currently available only for local mode

@Loocos commented on GitHub (Mar 27, 2022): > @Loocos could you try running appflowy with `DISPLAY=:0`? > > So like `DISPLAY=:0 docker run ...` Still same, I've tried everything. But I think I got the anwser by joining the discord, I found this issue : https://github.com/AppFlowy-IO/AppFlowy/issues/313 And that's what I'm trying to do. I want to host it and use it on my domain. But it's currently available only for local mode

mirror commented

2026-03-23 20:33:30 +00:00

Author

Owner

@MikeWallaceDev commented on GitHub (Mar 28, 2022):

@Loocos Please be advised that AppFlowy currently does not run as a web app...

@MikeWallaceDev commented on GitHub (Mar 28, 2022): @Loocos Please be advised that AppFlowy currently does not run as a web app...

mirror commented

2026-03-23 20:33:30 +00:00

Author

Owner

@Loocos commented on GitHub (Mar 28, 2022):

@MikeWallaceDev Yes, I've read that after. So currently, can I host the solution on a linux based system (dedicated server) and use it for myself and a friend, then share/use docs between us in two different network ?
Thanks for your confirmation!

@Loocos commented on GitHub (Mar 28, 2022): @MikeWallaceDev Yes, I've read that after. So currently, can I host the solution on a linux based system (dedicated server) and use it for myself and a friend, then share/use docs between us in two different network ? Thanks for your confirmation!

mirror commented

2026-03-23 20:33:30 +00:00

Author

Owner

@MikeWallaceDev commented on GitHub (Jul 25, 2022):

@Loocos so sorry, I never saw this.

AF is currently a single user desktop application. We don't support multi-user yet.

However, what magic that you are able to do with symlinks and a cloud to share data, that's up to you. :) I've never tried it, and I have no clue what will happen if two users modify the pages at the same time.

@MikeWallaceDev commented on GitHub (Jul 25, 2022): @Loocos so sorry, I never saw this. AF is currently a single user desktop application. We don't support multi-user yet. However, what magic that you are able to do with symlinks and a cloud to share data, that's up to you. :) I've never tried it, and I have no clue what will happen if two users modify the pages at the same time.

mirror referenced this issue

2026-03-23 21:35:51 +00:00

[PR #179] [MERGED] Automate build sdk sh #4001