How to uninstall eclipse che completely on mac osx?
Used mac osx installer to install binary. Seems che is always running on 8080 even killed the process and stopped docker.
https://eclipse.org/che/
I couldn't find the better way for uninstall on Mac but you can stop the Tomcat embedded in Eclipse Che.
The path is /Applications/EclipseChe3.12.5.2.app/Contents/Resources/eclipse-che/tomcat/bin
Next step is stop the Tomcat instance and finally delete the folder EclipseChe3.12.5.2.app because that's my Eclipse Che version.
So, I hope this is helpfully for you
If you are using Docker the process is different.
Get the list of active instance in Docker by running the following command in Terminal: docker ps
Then you can stop the running instance by running in docker stop XXX where XXX is the name of the running container instance. You may have more than one container instance to stop.
Then you can remove it by running docker rm XXX and then you can list images that are present on your system by running docker images
If you want to completely remove Che, then pickup for the images list the ones that are related to che and remove them by running the following command: docker mi image_name
Last command to stop docker on your mac will be docker-machin stop environment_name. If you do not know the name of the running environment you can figure it out by running docker-machine ls
Related
With following setup:
ubuntu VM, running eclipse C/C++ IDE
ubuntu 16.04 docker container with PTXdist build system and gcc toolchain
source code in VM filesystem mounted to docker container
remote target connected via SSH
What works and what not:
PTXdist: build project from command line - OK, works
make: build project from command line - OK, works
gdb: from command line - attach to binary in running container works
eclipse:
debug configuration calls python script which executes docker gdb in running container
FAILED with timeout on gdb version
It looks like the gdb machine interface is not reachable from eclipse while checking the gdb version (as a connection test?).
Already tried to attach STDIN,STDOUT to the container, but without success.
Does anyone have a hint to configure this setup?
P.S. The next step will be to switch from ubuntu VM to Windows 10 (with Docker Desktop + WSL2)
I am traying to run docker-compose, but an error occur:
eric#pop-os:~/Documentos/web$ docker-compose up Postgres
bash: /home/eric/.local/bin/docker-compose: Arquivo ou diretório inexistente
When I run which docker-compose:
eric#pop-os:~/Documentos//web$ which docker-compose
/home/eric/.pyenv/shims/docker-compose
It is possible to change the path to docker-compose on Linux Pop Os to solve this problem?
I search on the web but not find any solution.
To solution this case I find 2 answers:
create an alias on ~/.bashrc --> but this solution gave me other problems.
When I installed docker-compose I installed it with pip. So
I uninstalled it and install docker-compose again but in the
operational system!
I have 5 images and try to run docker images through docker-compose up, but it is showing nothing on the console.
while running the docker-compose --version it is showing nothing.
docker-compose does not come bundled with the docker-engine. You need to install it separately after installing the engine. Follow the instructions given in this link:
https://docs.docker.com/compose/install/
I am new to vagrant and I keep getting this error.
How can I properly run vagrant up so that I can continue with the setup process?
so once you have Vagrant and VirtualBox installed, the next steps are to create a Vagrantfile which basically is the configuration file for the VM you will build. It contains box information as well as network, sync folder and any provisioning you'll do on the VM.
for example, if you want to create an ubuntu VM:
$ vagrant init <ubuntu/wily64>
$ vagrant up
The first command (vagrant init) might take some time as it will download a VM from internet but you only run it once. then vagrant up will boot the VM
For Linux installer, we have added a custom launcher for auto start of service (see pic below).
We are using install4j v5.1.6. It creates a link in /etc/init.d/myService.sh which points to the /bin/myService.sh .
It works properly in Ubuntu 13. On system restart, service auto starts properly.
On Ubuntu 14 this doesn't work. Service starts first time after installation. But on system restart, service doesn't auto start.
On further investigation, running these commands on Ubuntu 14 enabled auto start.
after installation
cd /etc/init.d
sudo update-rc.d myService.sh defaults
Under installer, install a service, auto start is set to true.
Is this a limitation of install4j that it doesn't register with update-rc.d ?
Do we know on which Linux systems copying to /etc/init.d/ is sufficient ?
Our script is similar to : www.shayanderson.com/linux/add-startup-script-or-service-with-linux-on-bootup.htm . What we don't have is update-rc.d and chkconfig. And install4j does the task of copying it to /etc/init.d/
Thanks !
http://s27.postimg.org/o5bih55kz/Launcher_Configuration.png
http://s3.postimg.org/icitxy96b/Launcher_Setup.png
As of 5.1.x, install4j does not integrate services into runlevels, it only creates the symlink to the start script in /etc/init.d.
Integrating it into runlevels has to be done manually, such as by calling update-rc.d or whatever other tool the particular distribution provides.