Gnome 3.32 - Error occurred when fetching containers

[Brian-Chow]

Extension stopped working after upgrading to Gnome 3.32 with the error message "Error occured when fetching containers"

Gnome shell log (Alt+f2, lg, extensions) says Docker Integration has not emitted any errors.
docker ps works from a terminal

Uninstalling and reinstalling did not seem to resolve the issue.

[black2996]

same here on GS3.32, nothing appears in the logfile, I'm currently running docker 18.06ce from Canonial snap store, it works perfectly on 3.30

[jonafato]

@Brian-Chow There's a typo in the title here. It should say 3.32, 3.22.

[matejrisek]

I had the same issue and because of that created this PR -> https://github.com/gpouilloux/gnome-shell-extension-docker/pull/41 .

[gpouilloux]

Hi guys, can you give it another try with the latest release uploaded in Gnome Extensions? It includes the improvements from @quarksplitter

[black2996]

Hi guys, can you give it another try with the latest release uploaded in Gnome Extensions? It includes the improvements from @quarksplitter

reinstalled from Gnome Extensions, no icon appeared after installing or restarting gnome shell, still in ubuntu 19.04 GS3.32

[gpouilloux]

@black2996 After restarting Gnome Shell, do you have any logs? I usually run journalctl -xe to check them out

[AdamLeonSmith]

Similar result. I uninstalled, reinstalled, restart and checked syslog and see:

gnome-software[4819]: State change on user///shell-extension/docker_status_gpouilloux/* from available to installed is not OK

The icon is not available in the shell.

[black2996]

@black2996 After restarting Gnome Shell, do you have any logs? I usually run journalctl -xe to check them out

weird, I cannot see any log related to this extension no matter how I get access to any of the log files, forgot to say, gnome shell on ubuntu has been upgraded to 3.32.1

[pauldaustin]

I'm having the same issues after upgrading to Ubuntu 19.04. Here are the lines in the log.

Apr 24 12:20:39 rsserver1 gnome-shell[27388]: Some code accessed the property 'ENABLED_EXTENSIONS_KEY' on the module 'extensionSystem'. That property was defined with 'let' or 'const' inside the module. This was
Apr 24 12:20:39 rsserver1 gnome-shell[27388]: Error occurred when fetching containers
Apr 24 12:20:39 rsserver1 gnome-shell[27388]: TypeError: this._construct is not a function
Apr 24 12:20:39 rsserver1 gnome-software[28536]: State change on user/*/*/shell-extension/docker_status_gpouilloux/* from available to installed is not OK
Apr 24 12:20:41 rsserver1 gnome-shell[27388]: Error occurred when fetching containers
Apr 24 12:20:41 rsserver1 gnome-shell[27388]: TypeError: this._construct is not a function
Apr 24 12:20:52 rsserver1 org.gnome.Shell.desktop[27388]: Window manager warning: last_focus_time (1625476704) is greater than comparison timestamp (5926381).  This most likely represents a buggy client sending 

[SlavikZ]

There was small problem with PanelMenu initialization, https://github.com/gpouilloux/gnome-shell-extension-docker/pull/43 should fix it.

[gsiciliano]

Same for me. Using ubuntu 19.04 with gnome 3.32, no errors given when activate extension, but no icon is shown

[thawkins]

Has this been resolved yet, i just installed it from the extensions site onto fedora 30, and no error, but no icon. I cant see anything in journalctl other than this.

May 13 20:28:20 timdev02 org.gnome.Shell.desktop[2121]: Window manager warning: Window 0x5000543 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.

[SlavikZ]

You may take dockerMenu.js from https://github.com/gpouilloux/gnome-shell-extension-docker/pull/43 - this should resolve the issue

[thawkins]

Is it not possible to push a fixed version to the extensions site?

[EgonHoltz]

Hello guys, I'm with the same problem here. I saw the code and it seem to happens when it try to call a docker function. docker ps -a

If I type the same command on my terminal I got the error: Error loading config file: /home/---/.docker/config.json: stat /home/---/.docker/config.json: permission denied

This happens because I just access Docker commands using sudo cmd...

[thawkins]

If you use sudo, docker will be filling up your /var patition with layers and images, if you add yourself to the "docker" group and restart the docker daemon, then all that stuff will be stored in a hidden folder in your home directory, and you wont need to use sudo.

To transition

1. Close/remove all your images
2. Use "sudo docker system prune" to remove all root level images and layers in /var
3. add your self to the "docker" group.
4. Reboot or restart the docker daemon.
5. Now "docker run hello-world" without sudo, check it works.
6. Rebuild and rerun your images.
7. The extension should now be able to display actibe containers.

On Tue, May 14, 2019, 06:48 Egon Holtz notifications@github.com wrote:

Hello guys, I'm with the same problem here. I saw the code and it seem to happens when it try to call a docker function. docker ps -a

If I type the same command on my terminal I got the error: Error loading config file: /home/---/.docker/config.json: stat /home/---/.docker/config.json: permission denied

This happens because I just access Docker commands using sudo cmd...

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/gpouilloux/gnome-shell-extension-docker/issues/40?email_source=notifications&email_token=AAADRSJR46PRM2JS5ENSUCLPVHV3FA5CNFSM4HAS4MGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVJYWDI#issuecomment-492014349, or mute the thread https://github.com/notifications/unsubscribe-auth/AAADRSPYGW2B2SMYHJQ5JXLPVHV3FANCNFSM4HAS4MGA .

[gsiciliano]

I resolve the issue using #43, but why don't create a branch from this PR only for Gnome Shell 3.32?

[thawkins]

Is there any action on this?, currently the extension is completly broken on fedora 30 and any other gnome 3.32 distro.

[EgonHoltz]

Thanks thawkins,

It help me a lot... Just to add information, I used the command to add my user to docker group: sudo usermod -aG docker $USER Then, I logged out and logged in.

It works!

If you use sudo, docker will be filling up your /var patition with layers and images, if you add yourself to the "docker" group and restart the docker daemon, then all that stuff will be stored in a hidden folder in your home directory, and you wont need to use sudo. To transition 1. Close/remove all your images 2. Use "sudo docker system prune" to remove all root level images and layers in /var 3. add your self to the "docker" group. 4. Reboot or restart the docker daemon. 5. Now "docker run hello-world" without sudo, check it works. 6. Rebuild and rerun your images. 7. The extension should now be able to display actibe containers. … On Tue, May 14, 2019, 06:48 Egon Holtz @.***> wrote: Hello guys, I'm with the same problem here. I saw the code and it seem to happens when it try to call a docker function. docker ps -a If I type the same command on my terminal I got the error: Error loading config file: /home/---/.docker/config.json: stat /home/---/.docker/config.json: permission denied This happens because I just access Docker commands using sudo cmd... — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#40?email_source=notifications&email_token=AAADRSJR46PRM2JS5ENSUCLPVHV3FA5CNFSM4HAS4MGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVJYWDI#issuecomment-492014349>, or mute the thread https://github.com/notifications/unsubscribe-auth/AAADRSPYGW2B2SMYHJQ5JXLPVHV3FANCNFSM4HAS4MGA .

[jagibson]

You may take dockerMenu.js from #43 - this should resolve the issue

This worked for me until a new release is pushed to the extensions website. I'm running Ubuntu 19.04.

[Brian-Chow]

Using PR #43 fixed the issue for me as well.