vmware / vmware/photon

Problems with docker and docker-machine

Open
#1,238 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

4.0 docker
Dominant language
C
Stars
3.2k
Forks
692
PR merge metrics
No merged PRs in 30d

Description

Hi,

I had a docker swarm cluster running with Photon OS 3. Because sometime some machines became instable I decided to test new OS version 4. After upgrade one worker to Photon version 3 I have problems with that machine:

  1. "docker-machine ls" shows a timeout for that machine
  2. "docker-machine evn machine" show and error telling:
    Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "10.224.108.221:2376": dial tcp 10.224.108.221:2376: i/o timeout
    You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
    Be advised that this will trigger a Docker daemon restart which might stop running containers.
  3. If I try to regenerate certs I get:
    Regenerating TLS certificates
    Waiting for SSH to be available...
    Detecting the provisioner...
    OS type not recognized
  4. Even doing the process manually it doesn't work
  5. Portainer show the tasks in that machine but without the "stats" and "exec console" action icons.

Maybe is the same issue as: https://unix.stackexchange.com/questions/663511/cant-connect-to-docker-containers-running-on-photon-os-4-0-linux-server or https://github.com/vmware/photon/issues/1082

Can anyone help on this?

thanks

Ignacio

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the docker-machine ls, docker-machine env, and docker-machine regenerate-certs failures against the Photon OS 4 worker, especially the timeout and “OS type not recognized” output. Compare the behavior with the linked Photon issue and reproduce the Portainer symptoms; done means the worker is reachable, certificates regenerate, and its management actions work.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, linux
Domain
devops, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.