Hi all
showing my ignorance a bit here, and this is probably a 'how long is a piece of strong' question...
I have a lenovo USFF box running a few apps as docker containers - nextcloud, a kanban board, issue tracker, things like that. It all works, but managing it all via ssh-ing in and manipulation of the docker-compose.yaml files feels a bit ... fragile.
I'd like to improve this but am not very clear about the best way to go.sake of it, as it were...
Do I just need something like a Docker Desktop, or Portainer, or would I benefit from eg. running Proxmox? the latter sounds like it might be an new interesting learning curve, but I don't necessarily want to go down too many rabbit holes just fro the
I have a lenovo USFF box running a few apps as docker containers -
nextcloud, a kanban board, issue tracker, things like that. It all works, but managing it all via ssh-ing in and manipulation of the docker-compose.yaml files feels a bit ... fragile.
I'd like to improve this but am not very clear about the best way to go.
Do I just need something like a Docker Desktop, or Portainer, or would I benefit from eg. running Proxmox? the latter sounds like it might be an
new interesting learning curve, but I don't necessarily want to go down
too many rabbit holes just fro the sake of it, as it were...
Hi allsake of it, as it were...
showing my ignorance a bit here, and this is probably a 'how long is a piece of strong' question...
I have a lenovo USFF box running a few apps as docker containers - nextcloud, a kanban board, issue tracker, things like that. It all works, but managing it all via ssh-ing in and manipulation of the docker-compose.yaml files feels a bit ... fragile.
I'd like to improve this but am not very clear about the best way to go.
Do I just need something like a Docker Desktop, or Portainer, or would I benefit from eg. running Proxmox? the latter sounds like it might be an new interesting learning curve, but I don't necessarily want to go down too many rabbit holes just fro the
[repost, as the first one didn't appear]
I hadn't heard of the DOCKER-HOST environment variable, thanks for that.
The first reply in my google search said something like "it is rarely a good idea
to set DOCKER-HOST" ;-). I'm not very clear if there are then standardised ways of
using the HTTP API, or you have to roll your own for each service?
On Saturday, December 23, 2023 at 12:40:56 AM UTC, Pancho wrote:
On 18/12/2023 20:57, jkn wrote:
I hadn't heard of the DOCKER-HOST environment variable, thanks for that. >>> The first reply in my google search said something like "it is rarely a good ideaMy apologies, DOCKER_HOST has been superseded (circa 2020-2021?) by the
to set DOCKER-HOST" ;-). I'm not very clear if there are then standardised ways of
using the HTTP API, or you have to roll your own for each service?
"docker context" commands. "docker context" is clearly better, it caters
for many remote contexts, and is usable from the command line via the
--context argument.
Having the DOCKER_HOST environment variable set overrides docker context
operations, silently. Which I guess is why you are seeing warnings not
to use it. I will stop using DOCKER_HOST now, and use docker context
instead.
I dunno what you mean by HTTP API?
Hmm - I'm a bit confused now. IIUC then setting DOCKER-HOST allows you
to use the 'HTTP API' to access the docker daemon (eg from a remote machine).
So instead of ssh'ing, you can send requests (eg. via curl, or your browser) to
monitor and control your docker images. That all makes sense, but since you were advocating the use of this I am surprised you are puzzled by the use of the term 'HTTP API'?
'docker context' seems to be something different?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 416 |
Nodes: | 16 (2 / 14) |
Uptime: | 83:02:10 |
Calls: | 8,739 |
Calls today: | 2 |
Files: | 13,282 |
Messages: | 5,961,253 |