docker-tutorial | React front-end and Node | Runtime Evironment library

The important detail here is that your React application isn't actually running in a container. It's running in the end user's browser, which is outside Docker space, and so doesn't have access to Docker's internal networking.

Say you have a typical application:

the issue is with the apostrophe ' you should be using apostrophes (in plural - otherwise known as quotation marks) "

(no changes needed on your behalf):

docker container commit --change="CMD ['java','-jar','/tmp/mytroubleartifact-0.jar']" upbeat_brahmagupta a-repo-name-of-choice/some-app-name:tagname2

though I've seen other people using a single apostrophe for me it also didn't work with your situation. docker docs example also didnt work with just copying the --change part, with both options (-c, --change) and with just one of them, only using double qoutes did the trick, not exactly sure why though. (tried replacing names, making them shorter ¯_(ツ)_/¯)

docker commit --change='CMD ["apachectl", "-DFOREGROUND"]' -c "EXPOSE 80" c3f279d17e0a svendowideit/testimage:version4

thanks to these posts for the working example:

https://adamtheautomator.com/docker-commit/ https://docs.oracle.com/cd/E37670_01/E75728/html/ch04s18.html

I feel this is a very valid question, but without a very specific answer as provided by the OP.

I would like to extend this to container tools not be specific to docker. Docker will be used as an example.

I feel the answer is already answered here(provided by OP) -> https://docs.microsoft.com/en-us/visualstudio/containers/overview?view=vs-2019

The tools included in Visual Studio for developing with containers are easy to use, and greatly simplify building, debugging, and deployment for containerized applications. You can work with a container for a single project, or use container orchestration with Docker Compose, Service Fabric, or Kubernetes to work with multiple services in containers.

It does not only add the dockerfiles. We are getting other capabilities as well most probably specific to Visual Studio which allow for building and debugging with the aka F5 experience as mentioned above. Also, we can append to it with orchestrators such as Docker-Compose, Service Fabric and Kubernettes again with building and debugging capabilities with F5.

As it can be seen very quickly by the below image, by just creating & enabling docker and docker compose orchestration support I am able to start the application using docker compose with F5 and also I have debugging capabilities out of the box. Also I can append to it with other services and add to the orchestrator with auto gen tools. Visual studio for most of these things will prompt to the user and it will fill Dockerfile and docker-compose files automatically. So we do not have to write any of the boilerplate infrastructure code.

There is some difference in the templates, not really though, since you can add docker & orchestration support later in the project with some extra clicks. So you do not have to do it from the start

I think that plugin requires the docker cli to be present. If you run jenkins as a docker image itself, use an image that provides the docker cli, for example https://hub.docker.com/r/trion/jenkins-docker-client

If you want to use the host docker daemon for building, you need to bind-mount the docker socket. If you want to use a sidecar container to provide the docker daemon, for example using a docker-in-docker setup you can usually use the container name as docker host or kubernetes service name. This depends on how you provide the sidecar container and there is no general answer to that.

you should:

Remove the slash character from the command, i.e.:

The command being docker run and not run, I suspect there might be some typo, maybe a non-printable character.

Try to type the complete command from a fresh prompt.

The reason why it failed because the dependencies used by golang program are not available inside docker for it to build successfully.

You are using dep for dependency management i.e. for your external libraries locally but have not installed any of them in the docker.

You need to have them available in docker by having first dep tool within your container. The dep tool will ensure that your dependencies required by the package are available by dep ensure

Also, you should ideally put your repository in the $GOPATH as mentioned below

The dockerfile will need these commands:

I'm suspecting the first line in Dockerfile tries to use the latest Ubuntu version 20.04, that doesn't have the package.

Change to version 18.04 and it will work: