- 新しい順
- 投票が多い順
- コメントが多い順
Hello,
From the details provided I understand that are experiencing issue to load the network service on the resource you use to run Docker containers. I assume that the errors provided came from the base Operating System, and not from the container itself. Configuration changes or dependencies required by the container service might have improperly modified the base network configurations.
If your host Operating System runs on EC2, you can try the following
- Use the serial console to troubleshoot your instance: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/troubleshoot-using-serial-console.html
- Besides serial console, you can also try EC2 rescue or troubleshoot the network issue via a recovery instance. Please review https://repost.aws/knowledge-center/ec2-linux-status-check-failure-os-errors , specifically ""Methods" 2 and 3 and "Bringing up interface eth0."
If your base Operating System runs on Workspaces , you may want to restore it. Quoting the Workspaces Documentation:
Restoring a WorkSpace recreates both the root volume and user volume, based on the most recent snapshots of these volumes that were created when the WorkSpace was healthy
I hope it helps
