I was given a .NET Core project to run in a Linux Docker container to do the build, everything seems to be okay on the docker configuration side, but when I run this command: dotnet publish -c Release -o out, I get the SSL authentication error below. The SSL connection could not be established, see inner exception. Authentication failed because
Tag: docker
How to pass backtick to Dockerfile CMD?
I have a docker image running java application, its main class is dynamic, in a file called start-class. Traditionally, I started the application like this. Now I want to run these applications in docker containers. This is my Dockerfile. I built the image and run the containers. The command actually executed was this. Single quotes was automatically wrapped outside the
`sudo` with command substitution
I’m working with a remote machine that requires sudo for most docker commands. I often have to perform multiple repetitive commands to stop docker containers, etc: sudo docker stop <container_name>. Normally, I’d use docker stop $(docker ps -q) to stop all the results of docker ps -q, but simply prefixing this with sudo doesn’t do what I’m after: sudo docker
How to run a dockerfile?
Found a dockerfile that want to create image and run: https://gist.github.com/matsuu/d5b4e83b3d591441f01b7be2ede774e2 Stored it in a new folder as centos-redhat-8-beta.dockerfile on my computer and tried: What is exact command that need to run? Answer Dockerfile is not an extension, per default the file should be called Dockerfile for the build command to use it. If you want to use a different
yum dependency resolution behaves differently in docker build vs docker run
It appears that yum’s dependency resolution behaves differently depending on whether it is invoked from the RUN statement of a Dockerfile, or from docker run. Consider this Dockerfile: The docker build fails on the last command. The full output is included below, but basically yum selects packages for both i386 and x86_64. But running the same commands from docker run
My container isn’t finding the package.json to execute npm install on docker-compose
I’m trying to deploy an application using docker-compose and the app is in a folder in the host machine (in the same dir that the docker-compose file). I’m runnig the command docker-compose up -d, however, it seems that the volume isn’t mounting because when the command npm install is executed the following message is displayed: After that my container is
Using $() in docker commands doesn’t seem to work
I want to stop all running docker containers with the command sudo docker stop $(docker ps -a -q). But when I run it, docker outputs Just running docker ps -a -q outputs the Docker IDs, but when I combine it with a Docker command, it doesn’t work. Thank you. Answer I didn’t realize that the sudo is required in the
ls sort order inside container
Running ls -d to list directories, print directories in different order if trailing / is present in file name. Why is that? What sorting rules apply? and why does this happen only with docker? With trailing / Without trailing / Answer I found out I get the same behavior using sort command But the sorting order changes when using sort
Started container with docker run, now it is not showing up in docker ps -a
I started a docker container with docker run, like this: Link to GitHub.com/plexinc/pms-docker The docker container is running, as Im able to access the port and service, but I can’t seem to list the container when Im running sudo docker ps -a or sudo docker ps -aq or sudo docker ps –filter “name=plex” I tried to run pstree, and got
Bash get docker image ID automatically
I’m trying to run a few docker commands in my linux machine: But I would like to make a runme.sh and execute all in one run. The problem is that ImageID bf46cff9b182 is dynamiccally changing everytime. So I need to somehow pipe it from the output of the load command, which is in fact possible. The output of load is