pycharm error running, cannot find runner on docker debug - docker

I am trying to debug docker image on pycharm, but getting this kind error.
error running 'docker_image_config'
cannot find runner for 'docker_image_config'
When I run docker_image_config, it runs well, but when I try to debug, it shows the above error.
Is there anyone who knows how to solve this problem ?
Please help me!!!

Related

Having issues with all ASK CLI commands not working

Every ASK CLI command that I try to run, whether in CMD or Powershell, aborts and provides me with this error:
[Error]: TypeError: Cannot convert undefined or null to object
I have tried many versions of Node and ASK CLI to no avail. I'm not sure if I'm being foolish as there's no other instances of anyone having this issue with ASK CLI but any help would be appreciated, thanks.
Image of Error Message

Problem with Jenkins running Robot Framework script

I am trying to automate the execution of Robot Framework using Jenkins.
But when I run Jenkins I am receiving the error "Permission denied". You can see bellow the error's print screen.
Despite several attenpts Im not able to identify where this restriction is.
I have already include the Jenkins user as SUDO user, but the error is still there.
I also applied o CHMOD 777 /home/eduardo/.local/bin/robot but did not solve.
Can someone please tell me how I can identify where this restriction (Permission denied) is.
Thank in advance.

Docker-compose throwing error

Hello guys I'm trying to get my vagrant up but the docker keeps on throwing an error which is given below :
Can't find a suitable configuration file in this directory or any parent. Are you in the right directory
The file is present at the root of my project. It was all working well but it just started to throw an error. Can somebody tell me what is it that I have done due to which I'm getting this error
well, I had this error but it was due to vagrant. If you are running vagrant then first of all enter into your vagrant machine using :
vagrant ssh command
and try to find the file over there. If you don't have it over there then this is the problem. That file is not being loaded over here because of which you are getting this error.
My error was coming because vagrant was not mounting the nfs partition because of which the whole project was not loading in the vagrant machine and after that, the docker command was being run. Since the project was not being loaded docker command was not able to find the required file.
If this is your problem try to mount your nfs partition first.
Run:
docker-compose -f rootoftheprojectpath/docker-compose.yml up -d
Check read permissions, typos, etc. Also check that your file is not empty
Regards

Bazel test fails while running "bazel test tensorflow_serving/..."

I am trying to setup TensorFlow Serving using Docker on a Windows machine by following the instructions from https://tensorflow.github.io/serving/docker.html
I have successfully built and run the container and cloned the TensorFlow servings sub-modules. However, while running the command
"bazel test tensorflow_serving/..." the error
Linking of rule: '//tensorflow_serving/batching/test_util:puppet_batch_scheduler_test' failed:gcc failed: error executing command /usr/bin/gcc .... is displayed
The complete stack trace is shown in the below image.
Any help is appreciated.
I don't know how to solve the problem directly, but a workaround could be pulling a docker image where the TF Serving is already compiled such as this one.

Can not write to '/dev/tty' when build Docker images

I'm building docker images from Dockerfile and when I run a script(CUDA installation script) which has
echo XXX > /dev/tty
in it, then an error "/dev/tty: No such device or address" comes up and the build failed.
I've tried --silent flag but it seems do no help.
My base image is Cent OS 7.
Is there anyway to fix or work around this?
I've fixed this problem: it turns out I didn't install command tar & perl before hand.
And the script wants to write error messages to /dev/tty.
The error information led me to the wrong way to solve this issue.
Thanks.

Resources