Can't run elastic beanstalk app locally using eb local run command - node.js
I followed the Elastic Beanstalk tutorial here
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_nodejs_express.html
And the app works perfectly fine when I deploy to EB; however, when I run eb local run it first complained about docker not being installed and needing version 1.6.0. I used homebrew to install the latest version, which is 4.16.2! I also boot2docker as it had suggested.
So, now I run the command eb local run and it complains with the following error
ERROR: NotSupportedError - You can use "eb local" only with preconfigured, generic and multicontainer Docker platforms.
Based on what I've gathered from other posts about similar issues, it may have to do with the default_platform in my .elasticbeanstalk/config.yml file, but that may just be a red-herring. The AWS documentation feels like it's very outdated.
Output of eb local run --debug
2023-02-02 18:53:52,934 (DEBUG) cement.core.foundation : laying cement for the 'eb' application
2023-02-02 18:53:52,934 (DEBUG) cement.core.hook : defining hook 'pre_setup'
2023-02-02 18:53:52,934 (DEBUG) cement.core.hook : defining hook 'post_setup'
2023-02-02 18:53:52,935 (DEBUG) cement.core.hook : defining hook 'pre_run'
2023-02-02 18:53:52,935 (DEBUG) cement.core.hook : defining hook 'post_run'
2023-02-02 18:53:52,935 (DEBUG) cement.core.hook : defining hook 'pre_argument_parsing'
2023-02-02 18:53:52,935 (DEBUG) cement.core.hook : defining hook 'post_argument_parsing'
2023-02-02 18:53:52,935 (DEBUG) cement.core.hook : defining hook 'pre_close'
2023-02-02 18:53:52,935 (DEBUG) cement.core.hook : defining hook 'post_close'
2023-02-02 18:53:52,935 (DEBUG) cement.core.hook : defining hook 'signal'
2023-02-02 18:53:52,935 (DEBUG) cement.core.hook : defining hook 'pre_render'
2023-02-02 18:53:52,935 (DEBUG) cement.core.hook : defining hook 'post_render'
2023-02-02 18:53:52,935 (DEBUG) cement.core.hook : registering hook 'add_handler_override_options' from cement.core.foundation into hooks['post_setup']
2023-02-02 18:53:52,935 (DEBUG) cement.core.hook : registering hook 'handler_override' from cement.core.foundation into hooks['post_argument_parsing']
2023-02-02 18:53:52,935 (DEBUG) cement.core.handler : defining handler type 'extension' (IExtension)
2023-02-02 18:53:52,935 (DEBUG) cement.core.handler : defining handler type 'log' (ILog)
2023-02-02 18:53:52,935 (DEBUG) cement.core.handler : defining handler type 'config' (IConfig)
2023-02-02 18:53:52,935 (DEBUG) cement.core.handler : defining handler type 'mail' (IMail)
2023-02-02 18:53:52,935 (DEBUG) cement.core.handler : defining handler type 'plugin' (IPlugin)
2023-02-02 18:53:52,935 (DEBUG) cement.core.handler : defining handler type 'output' (IOutput)
2023-02-02 18:53:52,935 (DEBUG) cement.core.handler : defining handler type 'argument' (IArgument)
2023-02-02 18:53:52,935 (DEBUG) cement.core.handler : defining handler type 'controller' (IController)
2023-02-02 18:53:52,935 (DEBUG) cement.core.handler : defining handler type 'cache' (ICache)
2023-02-02 18:53:52,935 (DEBUG) cement.core.handler : registering handler '<class 'cement.core.extension.CementExtensionHandler'>' into handlers['extension']['cement']
2023-02-02 18:53:52,944 (DEBUG) cement.ext.ext_plugin : plugin config dir /etc/eb/plugins.d does not exist.
2023-02-02 18:53:52,944 (DEBUG) cement.ext.ext_plugin : plugin config dir /Users/username/.eb/plugins.d does not exist.
2023-02-02 18:53:52,947 (DEBUG) ebcli.core.hooks : -- EBCLI Version: 3.20.3
2023-02-02 18:53:52,947 (DEBUG) ebcli.core.hooks : -- Python Version: 3.10.9 (main, Feb 2 2023, 17:23:54) [Clang 13.1.6 (clang-1316.0.21.2.5)]
2023-02-02 18:53:52,947 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/username/Documents/GitHub/server
2023-02-02 18:53:52,949 (DEBUG) ebcli.objects.sourcecontrol : Getting current branch name by performing `git rev-parse --abbrev-ref HEAD`
2023-02-02 18:53:52,968 (DEBUG) ebcli.objects.sourcecontrol : master
2023-02-02 18:53:52,968 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/username/Documents/GitHub/server
2023-02-02 18:53:52,969 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/username/Documents/GitHub/server
2023-02-02 18:53:52,970 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/username/Documents/GitHub/server
2023-02-02 18:53:52,971 (DEBUG) ebcli.objects.sourcecontrol : Getting current branch name by performing `git rev-parse --abbrev-ref HEAD`
2023-02-02 18:53:52,977 (DEBUG) ebcli.objects.sourcecontrol : master
2023-02-02 18:53:52,977 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/username/Documents/GitHub/server
2023-02-02 18:53:52,978 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/username/Documents/GitHub/server
2023-02-02 18:53:52,979 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/username/Documents/GitHub/server
2023-02-02 18:53:52,980 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/username/Documents/GitHub/server
2023-02-02 18:53:52,981 (DEBUG) ebcli.lib.utils : docker --version
2023-02-02 18:53:53,111 (DEBUG) ebcli.lib.utils : Docker version 20.10.22, build 3a2c30b
2023-02-02 18:53:53,123 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/username/Documents/GitHub/server
2023-02-02 18:53:53,125 (DEBUG) ebcli.objects.sourcecontrol : Getting current branch name by performing `git rev-parse --abbrev-ref HEAD`
2023-02-02 18:53:53,132 (DEBUG) ebcli.objects.sourcecontrol : master
2023-02-02 18:53:53,132 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/username/Documents/GitHub/server
2023-02-02 18:53:53,133 (DEBUG) ebcli.core.fileoperations : Project root found at: /Users/username/Documents/GitHub/server
2023-02-02 18:53:53,134 (DEBUG) ebcli.lib.elasticbeanstalk : Inside list_platform_branches api wrapper
2023-02-02 18:53:53,134 (DEBUG) ebcli.lib.aws : Creating new Botocore Session
2023-02-02 18:53:53,134 (DEBUG) ebcli.lib.aws : Botocore version: 1.23.54
2023-02-02 18:53:53,138 (DEBUG) ebcli.lib.aws : Creating new Botocore Client for elasticbeanstalk
2023-02-02 18:53:53,372 (DEBUG) ebcli.lib.aws : Successfully created session for elasticbeanstalk
2023-02-02 18:53:53,372 (DEBUG) ebcli.lib.aws : Making api call: (elasticbeanstalk, list_platform_branches) to region: us-east-2 with args:{'Filters': [{'Attribute': 'BranchName', 'Operator': '=', 'Values': ['Node.js 16']}]}
2023-02-02 18:53:54,561 (DEBUG) ebcli.lib.aws : API call finished, status = 200
2023-02-02 18:53:54,561 (DEBUG) ebcli.lib.aws : Response: {'PlatformBranchSummaryList': [], 'ResponseMetadata': {'RequestId': 'dab8c0e2-24ee-4091-aed3-714fa90425ae', 'HTTPStatusCode': 200, 'date': 'Fri, 03 Feb 2023 04:53:53 GMT', 'RetryAttempts': 0}}
2023-02-02 18:53:54,561 (DEBUG) ebcli.lib.elasticbeanstalk : Inside get_available_solution_stacks api wrapper
2023-02-02 18:53:54,561 (DEBUG) ebcli.lib.aws : Making api call: (elasticbeanstalk, list_available_solution_stacks) to region: us-east-2 with args:{}
2023-02-02 18:53:55,145 (DEBUG) ebcli.lib.aws : API call finished, status = 200
2023-02-02 18:53:55,146 (DEBUG) ebcli.lib.aws : Response: {'SolutionStacks': ['64bit Amazon Linux 2018.03 v2.12.0 running Ruby 2.3 (Puma)', '64bit Amazon Linux 2018.03 v2.12.0 running Ruby 2.2 (Puma)', '64bit Amazon Linux 2018.03 v2.12.0 running Ruby 2.1 (Puma)', '64bit Amazon Linux 2018.03 v2.12.0 running Ruby 2.0 (Puma)', '64bit Amazon Linux 2018.03 v2.12.0 running Ruby 2.3 (Passenger Standalone)', '64bit Amazon Linux 2018.03 v2.12.0 running Ruby 2.2 (Passenger Standalone)', '64bit Amazon Linux 2018.03 v2.12.0 running Ruby 2.1 (Passenger Standalone)', '64bit Amazon Linux 2018.03 v2.12.0 running Ruby 2.0 (Passenger Standalone)', '64bit Amazon Linux 2018.03 v2.12.0 running Ruby 1.9.3', '64bit Debian jessie v2.16.0 running Go 1.4 (Preconfigured - Docker)', '64bit Debian jessie v2.16.0 running Go 1.3 (Preconfigured - Docker)', '64bit Amazon Linux 2018.03 v3.4.0 running Tomcat 8 Java 8', '64bit Amazon Linux 2018.03 v3.4.0 running Tomcat 7 Java 6', '64bit Debian jessie v2.16.0 running Python 3.4 (Preconfigured - Docker)', '64bit Amazon Linux 2018.03 v2.9.11 running PHP 5.4', '64bit Amazon Linux 2018.03 v2.9.11 running PHP 5.5', '64bit Amazon Linux 2018.03 v2.9.11 running PHP 5.6', '64bit Amazon Linux 2018.03 v2.9.11 running PHP 7.0', '64bit Amazon Linux 2018.03 v2.9.11 running PHP 7.1', '64bit Amazon Linux 2018.03 v2.6.33 running Packer 1.0.3', '64bit Amazon Linux 2018.03 v2.9.15 running Python 3.4', '64bit Amazon Linux 2018.03 v2.9.15 running Python', '64bit Amazon Linux 2018.03 v2.9.15 running Python 2.7', '64bit Amazon Linux 2 v3.4.4 running Corretto 17', '64bit Amazon Linux 2 v3.4.4 running Corretto 11', '64bit Amazon Linux 2 v3.4.4 running Corretto 8', '64bit Amazon Linux 2 v2.5.0 running .NET Core', '64bit Amazon Linux 2 v3.4.4 running Python 3.8', '64bit Amazon Linux 2 v3.4.4 running Python 3.7', '64bit Amazon Linux 2 v5.6.4 running Node.js 16', '64bit Amazon Linux 2 v5.6.4 running Node.js 14', '64bit Amazon Linux 2 v3.2.4 running ECS', '64bit Amazon Linux 2 v3.5.4 running PHP 8.1', '64bit Amazon Linux 2 v3.5.4 running PHP 8.0', '64bit Amazon Linux 2 v3.5.4 running PHP 7.4', '64bit Amazon Linux 2 v3.5.4 running Docker', '64bit Amazon Linux 2 v3.6.3 running Ruby 3.0', '64bit Amazon Linux 2 v3.6.3 running Ruby 2.7', '64bit Amazon Linux 2 v3.6.4 running Go 1', '64bit Amazon Linux 2 v4.3.4 running Tomcat 8.5 Corretto 11', '64bit Amazon Linux 2 v4.3.4 running Tomcat 8.5 Corretto 8', '64bit Windows Server Core 2019 v2.11.0 running IIS 10.0', '64bit Windows Server 2019 v2.11.0 running IIS 10.0', '64bit Windows Server Core 2016 v2.11.0 running IIS 10.0', '64bit Windows Server 2016 v2.11.0 running IIS 10.0', '64bit Windows Server Core 2012 R2 v2.11.0 running IIS 8.5', '64bit Windows Server 2012 R2 v2.11.0 running IIS 8.5'], 'SolutionStackDetails': [{'SolutionStackName': '64bit Amazon Linux 2018.03 v2.12.0 running Ruby 2.3 (Puma)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.12.0 running Ruby 2.2 (Puma)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.12.0 running Ruby 2.1 (Puma)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.12.0 running Ruby 2.0 (Puma)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.12.0 running Ruby 2.3 (Passenger Standalone)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.12.0 running Ruby 2.2 (Passenger Standalone)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.12.0 running Ruby 2.1 (Passenger Standalone)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.12.0 running Ruby 2.0 (Passenger Standalone)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.12.0 running Ruby 1.9.3', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Debian jessie v2.16.0 running Go 1.4 (Preconfigured - Docker)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Debian jessie v2.16.0 running Go 1.3 (Preconfigured - Docker)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v3.4.0 running Tomcat 8 Java 8', 'PermittedFileTypes': ['war', 'zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v3.4.0 running Tomcat 7 Java 6', 'PermittedFileTypes': ['war', 'zip']}, {'SolutionStackName': '64bit Debian jessie v2.16.0 running Python 3.4 (Preconfigured - Docker)', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.9.11 running PHP 5.4', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.9.11 running PHP 5.5', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.9.11 running PHP 5.6', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.9.11 running PHP 7.0', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.9.11 running PHP 7.1', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.6.33 running Packer 1.0.3', 'PermittedFileTypes': []}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.9.15 running Python 3.4', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.9.15 running Python', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2018.03 v2.9.15 running Python 2.7', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v3.4.4 running Corretto 17', 'PermittedFileTypes': ['jar', 'zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v3.4.4 running Corretto 11', 'PermittedFileTypes': ['jar', 'zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v3.4.4 running Corretto 8', 'PermittedFileTypes': ['jar', 'zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v2.5.0 running .NET Core', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v3.4.4 running Python 3.8', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v3.4.4 running Python 3.7', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v5.6.4 running Node.js 16', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v5.6.4 running Node.js 14', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v3.2.4 running ECS', 'PermittedFileTypes': []}, {'SolutionStackName': '64bit Amazon Linux 2 v3.5.4 running PHP 8.1', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v3.5.4 running PHP 8.0', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v3.5.4 running PHP 7.4', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v3.5.4 running Docker', 'PermittedFileTypes': []}, {'SolutionStackName': '64bit Amazon Linux 2 v3.6.3 running Ruby 3.0', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v3.6.3 running Ruby 2.7', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v3.6.4 running Go 1', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v4.3.4 running Tomcat 8.5 Corretto 11', 'PermittedFileTypes': ['war', 'zip']}, {'SolutionStackName': '64bit Amazon Linux 2 v4.3.4 running Tomcat 8.5 Corretto 8', 'PermittedFileTypes': ['war', 'zip']}, {'SolutionStackName': '64bit Windows Server Core 2019 v2.11.0 running IIS 10.0', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server 2019 v2.11.0 running IIS 10.0', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server Core 2016 v2.11.0 running IIS 10.0', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server 2016 v2.11.0 running IIS 10.0', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server Core 2012 R2 v2.11.0 running IIS 8.5', 'PermittedFileTypes': ['zip']}, {'SolutionStackName': '64bit Windows Server 2012 R2 v2.11.0 running IIS 8.5', 'PermittedFileTypes': ['zip']}], 'ResponseMetadata': {'RequestId': 'a95879bd-2a54-4e7a-b70b-031ded370893', 'HTTPStatusCode': 200, 'date': 'Fri, 03 Feb 2023 04:53:53 GMT', 'RetryAttempts': 0}}
2023-02-02 18:53:55,156 (DEBUG) ebcli.lib.elasticbeanstalk : Solution Stack result size = 47
2023-02-02 18:53:55,165 (INFO) eb : Traceback (most recent call last):
File "/Users/username/.ebcli-virtual-env/lib/python3.10/site-packages/ebcli/core/ebrun.py", line 62, in run_app
app.run()
File "/Users/username/.ebcli-virtual-env/lib/python3.10/site-packages/cement/core/foundation.py", line 797, in run
return_val = self.controller._dispatch()
File "/Users/username/.ebcli-virtual-env/lib/python3.10/site-packages/cement/core/controller.py", line 472, in _dispatch
return func()
File "/Users/username/.ebcli-virtual-env/lib/python3.10/site-packages/cement/core/controller.py", line 472, in _dispatch
return func()
File "/Users/username/.ebcli-virtual-env/lib/python3.10/site-packages/cement/core/controller.py", line 478, in _dispatch
return func()
File "/Users/username/.ebcli-virtual-env/lib/python3.10/site-packages/ebcli/core/abstractcontroller.py", line 92, in default
self.do_command()
File "/Users/username/.ebcli-virtual-env/lib/python3.10/site-packages/ebcli/controllers/local.py", line 62, in do_command
cnt = factory.make_container(self.app.pargs.envvars,
File "/Users/username/.ebcli-virtual-env/lib/python3.10/site-packages/ebcli/containers/factory.py", line 76, in make_container
raise NotSupportedError(strings['local.unsupported'])
ebcli.objects.exceptions.NotSupportedError: You can use "eb local" only with preconfigured, generic and multicontainer Docker platforms.
Related
docker networking not working after installing Docker Desktop in Ubuntu
after I installed Docker Desktop on my linux machine, my docker containers don't work any more. The containers can't communicate with each others or connect to the internet.
I found the Self-diagnose tool. And when running this I get:
➜ ~ /opt/docker-desktop/bin/com.docker.diagnose check
[2022-10-21T21:53:23.963576537Z][com.docker.diagnose][I] set path configuration to OnHost
Starting diagnostics
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0034: is Context set to a Docker Desktop context?
[PASS] DD0003: is the Docker CLI working?
[FAIL] DD0014: are the backend processes running? 2 errors occurred:
* querying com.docker.backend process: is it running as a different user?: readlink /proc/22636/exe: permission denied
* querying com.docker.backend process: is it running as a different user?: readlink /proc/22654/exe: permission denied
[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[FAIL] DD0012: is the VM networking working? network checks failed: failed to ping host: exit status 1
[2022-10-21T21:53:24.648095036Z][com.docker.diagnose][I] ipc.NewClient: 4c9ff8fa-diagnose-network -> diagnosticd.sock diagnosticsd
[common/pkg/diagkit/gather/diagnose.runIsVMNetworkingOK()
[ common/pkg/diagkit/gather/diagnose/network.go:34 +0xd9
[common/pkg/diagkit/gather/diagnose.(*test).GetResult(0x11754a0)
[ common/pkg/diagkit/gather/diagnose/test.go:46 +0x43
[common/pkg/diagkit/gather/diagnose.Run.func1(0x11754a0)
[ common/pkg/diagkit/gather/diagnose/run.go:17 +0x5a
[common/pkg/diagkit/gather/diagnose.walkOnce.func1(0x2?, 0x11754a0)
[ common/pkg/diagkit/gather/diagnose/run.go:142 +0x77
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x1, 0x11754a0, 0xc000223728)
[ common/pkg/diagkit/gather/diagnose/run.go:151 +0x87
[common/pkg/diagkit/gather/diagnose.walkDepthFirst(0x0, 0x11755a0, 0xc000223728)
[ common/pkg/diagkit/gather/diagnose/run.go:148 +0x52
[common/pkg/diagkit/gather/diagnose.walkOnce(0xb0fde0?, 0xc00035f890)
[ common/pkg/diagkit/gather/diagnose/run.go:137 +0xcc
[common/pkg/diagkit/gather/diagnose.Run(0x11755a0, 0x7fbd50ef6300?, {0xc00035fb20, 0x1, 0x1})
[ common/pkg/diagkit/gather/diagnose/run.go:16 +0x1d4
[main.checkCmd({0xc00012e010?, 0x6?, 0x4?}, {0x0, 0x0})
[ common/cmd/com.docker.diagnose/main.go:133 +0x105
[main.main()
[ common/cmd/com.docker.diagnose/main.go:99 +0x2a7
[2022-10-21T21:53:24.648917178Z][com.docker.diagnose][I] (c88fef01) 4c9ff8fa-diagnose-network C->S diagnosticsd POST /check-network-connectivity: {"ips":["169.254.5.211","169.254.5.199","192.168.86.22"]}
[2022-10-21T21:53:25.180233483Z][com.docker.diagnose][W] (c88fef01) 4c9ff8fa-diagnose-network C<-S d6792b26-diagnosticsd POST /check-network-connectivity (531.701612ms): failed to ping host: exit status 1
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0037: is the virtiofs setup correct?
[PASS] DD0036: is the credentials store configured correctly?
[PASS] DD0033: does the host have Internet access?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0032: do Docker networks overlap with host IPs?
Please investigate the following 2 issues:
1 : The test: are the backend processes running?
Failed with: 2 errors occurred:
* querying com.docker.backend process: is it running as a different user?: readlink /proc/22636/exe: permission denied
* querying com.docker.backend process: is it running as a different user?: readlink /proc/22654/exe: permission denied
Not all of the backend processes are running.
2 : The test: is the VM networking working?
Failed with: network checks failed: failed to ping host: exit status 1
VM seems to have a network connectivity issue. Check your host firewall and anti-virus settings in case they are blocking the VM.
Docker version:
➜ ~ docker version
Client: Docker Engine - Community
Cloud integration: v1.0.29
Version: 20.10.20
API version: 1.41
Go version: go1.18.7
Git commit: 9fdeb9c
Built: Tue Oct 18 18:20:18 2022
OS/Arch: linux/amd64
Context: desktop-linux
Experimental: true
Server: Docker Desktop 4.13.0 (89412)
Engine:
Version: 20.10.20
API version: 1.41 (minimum version 1.12)
Go version: go1.18.7
Git commit: 03df974
Built: Tue Oct 18 18:18:35 2022
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.8
GitCommit: 9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6
runc:
Version: 1.1.4
GitCommit: v1.1.4-0-g5fd4c4d
docker-init:
Version: 0.19.0
GitCommit: de40ad0
The issues are right there, but I have no clue on how to fix this.
Kubernetes setup on centos 7 hangs
I have setup of 1 master and 2 salves of kubernetes on centos machines.
Also there is dashboard for kubernetes and 6 spring boot services. The mongodb is installed as service on master node.
The setup works fine for 1 or 2 days but then the system hangs and need to do the forceful restart. There are no memory or cpu panic logs or any kubernetes error logs available. The CPU and memory usage is 2% of total available.
Please can anyone suggest any issues with the setup. Below is the versions that i use:
Docker - Docker version 1.13.1, build 64e9980/1.13.1
CentOS -
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"```
**Kubernetes** -
```kubeadm version: &version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.4", GitCommit:"c96aede7b5205121079932896c4ad89bb93260af", GitTreeState:"clean", BuildDate:"2020-06-17T11:39:11Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}```
**mongodb** -
v4.0.19
Wirtual Machine with Windows Server from Azure doesnt run Linux based Docker Container
I try to run a Docker container based on Linux on Virtual Machine from Azure with Windows Server 2019.
I work with a lot of tutorials for that, I enabled experimental flags, so docker version show:
PS C:\Users\azure> docker version
Client: Docker Engine - Enterprise
Version: 19.03.5
API version: 1.40
Go version: go1.12.12
Git commit: 2ee0c57608
Built: 11/13/2019 08:00:16
OS/Arch: windows/amd64
Experimental: false
Server: Docker Engine - Enterprise
Engine:
Version: 19.03.5
API version: 1.40 (minimum version 1.24)
Go version: go1.12.12
Git commit: 2ee0c57608
Built: 11/13/2019 07:58:51
OS/Arch: windows/amd64
Experimental: true
And docker info:
docker info
Client:
Debug Mode: false
Plugins:
cluster: Manage Docker clusters (Docker Inc., v1.2.0)
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 4
Server Version: 19.03.5
Storage Driver: lcow (linux) windowsfilter (windows)
LCOW:
Windows:
Logging Driver: json-file
Plugins:
Volume: local
Network: ics internal l2bridge l2tunnel nat null overlay private transparent
Log: awslogs etwlogs fluentd gcplogs gelf json-file local logentries splunk syslog
Swarm: inactive
Default Isolation: process
Kernel Version: 10.0 17763 (17763.1.amd64fre.rs5_release.180914-1434)
Operating System: Windows Server 2019 Datacenter Version 1809 (OS Build 17763.1098)
OSType: windows
Architecture: x86_64
CPUs: 1
Total Memory: 2GiB
Name: xxx-yyy
ID: R2TB:P4GZ:MRU4:IU4A:BPTU:DPYY:GV7C:VNL3:JW6F:IRKJ:BTKW:BVNE
Docker Root Dir: C:\ProgramData\docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: true
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
But finally, when I run any Linux container I got this error:
PS C:\Users\azure> docker run --platform=linux hello-world:linux
docker : C:\Program Files\Docker\docker.exe: Error response from daemon: failed to start
service utility VM (createreadwrite): hcsshim::CreateComputeSystem
2410bb8b9e431b1068750d0c79376b1fdc196eef97c0a48ec8571775349acde7_svm: The virtual machine
could not be started because a required feature is not installed.
At line:1 char:1
+ docker run --platform=linux hello-world:linux
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (C:\Program File... not installed.:String) [],
RemoteException
+ FullyQualifiedErrorId : NativeCommandError
(extra info: {"SystemType":"container","Name":"2410bb8b9e431b1068750d0c79376b1fdc196eef97c0
a48ec8571775349acde7_svm","Layers":null,"HvPartition":true,"HvRuntime":{"ImagePath":"C:\\Pr
ogram Files\\Linux Containers","LinuxInitrdFile":"initrd.img","LinuxKernelFile":"kernel"},"
ContainerType":"linux","TerminateOnLastHandleClosed":true}).
See 'C:\Program Files\Docker\docker.exe run --help'.
I miss something in Azure? In VM config?
I solve my problem and it wasn't a problem with config, docker, or with Windows Server. The problem was hardware - when you select Azure processor you should use a processor with nested virtualization. The solution is described here: https://blog.darrenjrobinson.com/azure-vm-docker-createcontainer-error-0xc0370102/
JBOSS not running
I'm from Linux server background and very new to JBOSS. I'm trying to setup a IoT application server which requires JBOSS service to provide
a web interface for the application server.
But when i check the JBOSS server state it is showing 'starting', i need this to be 'running'.
# /opt/cgms/bin/jboss-cli.sh --connect controller=127.0.0.1 ":read- attribute(name=server-state)"
{
"outcome" => "success",
"result" => "starting"
}
I can see that the deployment is getting failed when i start JBOSS using the script standalone.sh. I've increased the deployment-timeout
up to 6000 seconds in standalone.xml, still the deployment is failing with the following message in /opt/cgms/standalone/deployments/cgms.ear.failed,
""JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [6000 seconds].
Check the server configuration file and the server logs to find more about the status of the deployment."
Here is my JBOSS setup details,
[root#app-server ~]# /opt/cgms/bin/jboss-cli.sh --connect
[standalone#localhost:9999 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /opt/cgms
JBoss AS release: 7.3.0.Final-redhat-14 "Janus"
JBoss AS product: EAP 6.2.0.GA
JAVA_HOME: null
java.version: 1.8.0_65
java.vm.vendor: Oracle Corporation
java.vm.version: 25.65-b01
os.name: Linux
os.version: 3.10.0-229.el7.x86_64
When i check the server.log, it is stuck at,
# tailf /opt/cgms/server/cgms/log/server.log
624: app-server: Aug 12 2017 05:45:01.506 +0000: %IOTFND-6-UNSPECIFIED: %[ch=StdSchedulerFactory][sev=INFO][tid=MSC service thread 1-1]: Quartz scheduler 'CgnmsQuartz' initialized from an externally provided properties instance.
625: app-server: Aug 12 2017 05:45:01.506 +0000: %IOTFND-6-UNSPECIFIED: %[ch=StdSchedulerFactory][sev=INFO][tid=MSC service thread 1-1]: Quartz scheduler version: 2.2.1
It will not go further from here.
I've tried with java 1.7, but the script standalone.sh failed with a java error,
java.lang.UnsupportedClassVersionError: com/cisco/cgms/loglayout/LogHandler : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:345)
at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:423)
at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261)
at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76)
Here are my server details,
OS - Red Hat Enterprise Linux Server release 7.1 (Maipo) - runs on Oracle VM VirtualBox
kernel - app-server 3.10.0-229.el7.x86_64 #1 SMP Thu Jan 29 18:37:38 EST 2015 x86_64 x86_64 x86_64 GNU/Linux
When i check netstat, port 80 and 443 are listening.
Please help to fix this problem.
system service is not started on fedora
Using the below code, I created a service
Code snippet from agentInstaller.sh
fileAgentController="agent_controller.sh"
if [[ "$os" = "debian" ]] ;then
update-rc.d $fileAgentController defaults
else
chkconfig --add /etc/init.d/$fileAgentController
fi
export start="start"
export command="/etc/init.d/$fileAgentController"
sh $command ${start}
Above code successfully start the service 'agent_controller.sh' on Amazon Linux AMI 2017.03 - amzn rhel fedora and Ubuntu 16.04.2 LTS
But give error with following machine details :-
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="7.3"
PRETTY_NAME="Red Hat Enterprise Linux Server 7.3 (Maipo)"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.3:GA:server"
Red Hat Enterprise Linux Server release 7.3 (Maipo)
I encountered following error on above machine :-
Reloading systemd: [ OK ]
Starting agent_controller.sh (via systemctl): Failed to start
agent_controller.sh.service: Unit not found.
[FAILED]