I am trying to use the new docker ecs feature, but just get an error 'ecs' is not a docker command.
Using the latest version of docker edge on macOS 10.15.7
Do I need some additional steps to activate the docker command?
For anyone who was following documentation they found about docker ecs written previous to some development changes - while it used to be a plugin, ECS integration is now part of the docker cli itself.
This document covers how to set it up using a context
https://docs.docker.com/engine/context/ecs-integration/
Related
I'm starting with JFrog Xray.
I created an account on JFrog cloud platform using my Github credentials.
I created an identity token for authentication.
I have a linux box with only terminal (No GUI).
In that I downloaded a project from Github and built a docker image from the source code.
Now I can see the images using command sudo docker images.
Now I installed the JFrog CLI using command
curl -fL https://getcli.jfrog.io\?setup | sh
The cli gets installed but as there is no browser, the integration with cloud does not happen.
Now I run the docker scan using the command
sudo jf docker scan <image-name> --url <url> --access-token <access-token>
The error I receive is as below
Get "api/v1/system/version": unsupported protocol scheme ""
Any help/ guidance is sincerely appreciated.
Thanks
The curl -fL https://getcli.jfrog.io?setup | sh command installs JFrog CLI and then initiates the jf setup command. The jf setup command does the following:
Opens the default browser, and allows you to sign in to a new and free JFrog environment in the cloud.
Configures JFrog CLI with the new JFrog instance connection details.
Since your Linux box includes no browser, I assume step #1 fails.
No worries though - Since the set up of a free JFrog environment requires a browser, here's what you can do to set up an environment and use it on your Linux box:
Set up the free JFrog environment in the cloud from a different machine with a browser installed, using this page - https://jfrog.com/start-free/#saas
Log into your new environment UI
Go to "Integrations" on the left menu panel
Copy the "JFrog CLI" installation command, and run it from your Linux box
This should get JFrog CLI installed and set up with your new JFrog environment.
Does VSCode dev containers support Dockerfiles where the base is a Windows Server Core base image? From looking at the docker build command, it seems that it assumes a Linux-based image.
Based on official documentation from here:
https://code.visualstudio.com/docs/remote/containers#_remote-containers-limitations :
"Windows container images are not yet supported."
I have a Db2 11.5 Trial Version image for installing db2 on RHEL7. I have no connectivity with the internet where docker installed and I want to configure db2 on docker with that 11.5 Trial Version image.
Is there any limitation to use only docker certified image for dockerization?.
There's no requirement that you use IBM's docker images when running Db2 in Docker. You can absolutely build your own Docker images from the standard installable code.
However, are you aware that you can "export" Docker images to using docker save and "import" them using docker import? This is certainly one way you could get IBM's official docker images on to a machine that does not have direct internet access.
Currently, I have:
a desktop with low system specs, Windows 7 Pro (without Admin Rights), without docker.
a Virtual Machine with Centos7, and docker installed.
On my desktop, I can either use:
my local installation of VSCode, and Remote - SSH to develop remotely on my VM. It works well, but I can't combine this with Remote - Containers.
X11Forwarding to develop directly with VSCode installed on this VM. I can use Remote - Containers, but X11 is very slow.
Is there a way, with local VSCode, to develop in a remote container, without local installation of docker (obviously with docker installed on the host)?
Is there a way, with local VSCode, to develop in a remote container,
without local installation of docker (obviously with docker installed
on the host)?
No. In the 'advanced containers' docs it says
You can use the Docker CLI locally with a remote Docker host by
setting local environment variables like DOCKER_HOST,
DOCKER_CERT_PATH, DOCKER_TLS_VERIFY. Since VS Code uses the Docker CLI
under the hood, you can use these same environment variables to
connect the Remote - Containers extension to the same remote host.
I added the bolding. Note that it is referring to the client not the remote there. This is from Developing inside a container on a remote Docker host.
Though not officially supported, it seems that it is possible to install Docker CLI without the daemon...
Is it possible to install only the docker cli and not the daemon
Maybe you can do this without admin?
That would, though, certainly be swimming against the grain. Probably your best bet is to stick with the 'remote - SSH' setup you've got going.
I just achieved this using the solution linked by #Tom (but with admin rights, I didn't test it without them)
I downloaded the docker-cli from the docker-cli-builder github repo and created the docker context successfully.
After selecting it in VSCode, it has started using the context allowing me to see the containers on the remote machine.
We have build a small tool called LiveSync which could solve your problem. You simply run
python3 -m pip install livesync
livesync <virtual-machine>
from inside your vscode workspace. It will start watching for changes and push them immediately to the remote. Hence you can code locally (even run your tests) and have all changes synced with your target system.
I'm looking for a way to integrate Docker containers with the Eclipse platform.
I would like to run all build/test/debug command inside containers and use same containers in Continuous Integration build and later in production.
The simplest way I looked on, was just to configure custom command but besides permissions problem (docker must run as sudo/root) it doesn't give me all the flexibility of real integration.
Any ideas on the best way to proceed?
it is not a full answer to your question but we (JBoss Tools team) started working on this and here are a few blogs about what is possible todo today and where we are with Eclipse docker tooling.
http://tools.jboss.org/blog/2015-03-02-getting-started-with-docker-and-wildfly.html
http://tools.jboss.org/blog/2015-03-03-docker-and-wildfly-2.html
http://tools.jboss.org/blog/2015-03-30-Eclipse_Docker_Tooling.html
To do that, i think you work on a Linux platform :-)
What i do for a classic java project :
Build a Docker image that contains a jdk and maven for example
In Eclipse, via "Run Configurations", create a "build in Docker" configuration that launch a command like this :
docker run --rm -v <eclipse_workspace_dir>:/usr/src/myapp -w /usr/src/myapp myrepo/myimage mvn clean install
it should work.
For your continuous integration, you can use Docker Jenkins plugin to do the same or with a sh script.
There is Docker Tooling for Eclipse, available from this update site (you also need to add this update site as for now).
Try Eclipse-Che
https://eclipse.org/che/
You can install it as a Docker runs.
These links were very useful to me :
https://github.com/docker/labs/blob/master/developer-tools/java-debugging/Eclipse-README.md
https://github.com/docker/labs/blob/master/developer-tools/java/chapters/ch07-eclipse.adoc
https://docs.docker.com/samples/
It is all about Tutorial: Debugging Java Applications in Docker, Install Docker Tooling in Eclipse
You can also Watch a quick video explaining the key steps in https://www.youtube.com/watch?v=XmhEZiS26os
To configure remote debugging in Eclipse, click on Run > Debug Configurations...
Tomcat for instance supports remote debugging the Java Platform Debugger Architecture (JPDA). Make sure that the remote debugging was enabled when the tomcat image (registration-webserver) was built.