I used a VM in Google Cloud Platform to host a Minecraft server, which I use ./run.sh to start the server. However, once I close the VM bash it shuts down my server. It's a way to keep my server running?
I tried using screen -S run.sh it didn't work though.
Related
I added a dockerhub image to the the Container Registry. Then, succesfully ran the image in Cloud Run. The image is https://hub.docker.com/r/atmoz/sftp. The thing is I'm unable to access the sftp server from FileZilla client.
Any thoughts on what could be going on? Any alternatives? I've considered running the image in a Compute Engine container so that I can actually generate a private key to use it to connect from the FileZilla client. Would appreciate to hear from your wisdom.
You can run an SFTP server in Cloud Run, but you cannot connect to the server.
The reason is that Cloud Run only supports HTTP Requests and responses. SFTP uses a different protocol (SSH) that is not supported by Cloud Run.
I'm running a fastapi server on ec2 ubuntu. Everything work fine when I ssh in to ec2 and run commands, but I want the server to be running when my local machine is off.
So, I tried AWS System manager's run command. The connection looks fine but when I cd to the server code and run ls it outputs nothing. Also, when I do poetry run python main.py in the server folder, which works totally perfect when I ssh in to the server from my local machine, it says poetry: not found.
Why is this happening. And is there another way I can run my server while being able to turn off my local machine.
There is not any kind of relation between your machine and your server in the cloud, and your ec2 its still alive and runs your services whenever you want
I am trying to host an Apache superset server on an Amazon EC2 instance. Whenever i host it from a standalone ssh, the moment i close the terminal from my laptop, the superset server shuts down..Is there a way i can host SuperSet server on Amazon EC2 instance so that it is online always ?
Run it using nohup superset <options> &. Then even after you close the terminal, it continues to run.
Stopping it should require kill the process using PID, which can be found using grep.
I can set up a ipython/jupyter notebook server on aws ec2 by following this tutorial, it starts the remote server by entering $jupyter notebook in the local terminal.
However I also saw a pre-configured community AMI graphlab-create, which will run the remote server without the need of a Linux/Unix ssh client at all.
I'm wondering how that could be realized, since some students may not have an access to a linux/unix system. Any hint is appreciated.
Using windows is not an issue. I hooked up to my notebook in AWS from my home computer. I have Windows 10.
You can link up to AWS using putty.
I am using a Ubuntu AMI.
Once you have a terminal open you simply follow the instruction you gave in your link
It worked like a charm for me.
Does anyone have an idea on steps of setting up an SSH tunnel for the CloudFoundry? I want to do remote debugging on cloud, but am blocked behind a firewall. So need to setup an SSH tunnel for that.
I wrote a blog post on setting up remote debugging for Java apps on Cloud Foundry. It covers using an SSH Tunnel to work around a firewall / NAT.
The answer from the article is this...
Obtain a public server.
Install SSHD. Edit /etc/ssh/sshd_config, add or set GatewayPorts to yes. Restart SSHD.
On your local machine run ssh -f -N -T -R 0.0.0.0:<public-port>:127.0.0.1:<debugger-port> <user>#<public-server-ip> (Windows users can use cygwin or possibly Putty, although the command will be different). This will instruct SSH to connect to the remote host, setup a reverse tunnel and go into the background. The reverse tunnel will listen on your public server on the port you specify (i.e. public-port) and forward traffic to the debugger port on your local machine. You can use different port numbers, but it is easiest if you just use the same port.
Start the debugger and listen on the same port (i.e. debugger-port) that you used in the SSH command.
Edit your manifest.yml file. Set JAVA_OPTS to -agentlib:jdwp=transport=dt_socket,address=<your-ip>:<your-port>.
Run cf push.
For a gentler walk through, see the post.