Using Eclipse CDT with Docker [message #1863133] |
Wed, 17 January 2024 19:33 |
Thomas McLeod Messages: 14 Registered: September 2012 |
Junior Member |
|
|
Hi has anyone attempted to build inside a docker container using Eclipse CDT? I installed the Eclipse Docker Tooling plugin and expected this to "just work," but I got the below error trying to run a test bash command instead of make. Eclipse is connecting to the container on unix:///var/run/docker.sock, and the connection is valid. It's apparently trying to run java -jar agent.jar and I do not know why.
12:15:24 **** Build of configuration Default for project S2VMS Github ****
[Running in image <devopsacicontainerregistry.azurecr.io/jenkins/netbox-bionic-aks-agent:latest>]
echo testing
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by hudson.remoting.jnlp.Main (file:/usr/share/jenkins/agent.jar)
WARNING: Please consider reporting this to the maintainers of hudson.remoting.jnlp.Main
WARNING: System::setSecurityManager will be removed in a future release
At least one -url option is required.
java -jar agent.jar [options...] <secret key> <agent name>
-agentLog FILE : Local agent error log destination
(overrides workDir)
-cert VAL : Specify additional X.509 encoded PEM
certificates to trust when connecting
to Jenkins root URLs. If starting with
@ then the remainder is assumed to be
the name of the certificate file to
read.
-credentials USER:PASSWORD : HTTP BASIC AUTH header to pass in for
making HTTP requests.
-direct (-directConnection) HOST:PORT : Connect directly to this TCP agent
port, skipping the HTTP(S) connection
parameter download. For example,
"myjenkins:50000".
-disableHttpsCertValidation : Ignore SSL validation errors - use as
a last resort only. (default: false)
-failIfWorkDirIsMissing : Fails the initialization if the
requested workDir or internalDir are
missing ('false' by default) (default:
false)
-headless : Run agent in headless mode, without
GUI (default: false)
-help : Show this help message (default: false)
-instanceIdentity VAL : The base64 encoded InstanceIdentity
byte array of the Jenkins controller.
When this is set, the agent skips
connecting to an HTTP(S) port for
connection info.
-internalDir VAL : Specifies a name of the internal files
within a working directory ('remoting'
by default) (default: remoting)
-jar-cache DIR : Cache directory that stores jar files
sent from the controller
-loggingConfig FILE : Path to the property file with
java.util.logging settings
-noKeepAlive : Disable TCP socket keep alive on
connection to the controller.
(default: false)
-noreconnect : If the connection ends, don't retry
and just exit. (default: false)
-protocols VAL : Specify the remoting protocols to
attempt when instanceIdentity is
provided.
-proxyCredentials USER:PASSWORD : HTTP BASIC AUTH header to pass in for
making HTTP authenticated proxy
requests.
-tunnel HOST:PORT : Connect to the specified host and
port, instead of connecting directly
to Jenkins. Useful when connection to
Jenkins needs to be tunneled. Can be
also HOST: or :PORT, in which case the
missing portion will be auto-configured
like the default behavior
-url URL : Specify the Jenkins root URLs to
connect to.
-version : Shows the version of the remoting jar
and then exits (default: false)
-webSocket : Make a WebSocket connection to Jenkins
rather than using the TCP port.
(default: false)
-webSocketHeader NAME=VALUE : Additional WebSocket header to set, eg
|
|
|
Powered by
FUDForum. Page generated in 0.04137 seconds