Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
As the service is obviously running, most likely cause for the issue that you have described is, that your user account does not have root privileges. To run "docker ps" you must either have root privileges or use the "sudo" prefix command for temporary root permissions. Alternatively you can add your user to the docker group on your system, like "sudo usermod -aG docker $(whoami)".
Well, the containers are actually "always on" (when they are running), but if you have set "automatic port mapping", they might use different ports each time they are running (if they need ports at all). What you will need to do is to choose "manual port mapping", then set a port and then create a proxy rule from the "Docker Proxy Rules" icon of the corresponding subscription. This way you can tell the server to translate incoming requests on e.g. a standard port to the specific port of the Docker container you are using on that site. More information on that: https://docs.plesk.com/en-US/onyx/a...esk-administration/using-docker.75823/#o77139
Maybe I wasn't clear, I have no issues in using the containers, even via Docker Proxy Rules, but the containers themselves can't reach the internet or resolve DNS queries, like if their networking bridge is host-only.
I think it is a known docker issue on Ubuntu with name resolution. A solution for that is described here (see last post in that thread): https://github.com/docker/docker/issues/1809