Unknown is simply what it then prints as the host name This is distinct from i looked it up, but it doesn't seem to correspond to anything which is what happens outside the container To be perfectly explicit, connecting to the host succeeded, but looking up its name. My approach is as follows I am trying to learn how to read netcdf files using python in the most easiest/fastest way I heard that it can be done with 3 lines of code but i really don't know how
I am running the mitgcm num. I'm trying to convert a netcdf file to either a csv or text file using python I have read this post but i am still missing a step (i'm new to python) It's a dataset including latitude, longitude,. Nc is the wrong tool for this job (to a greater or lesser degree based on which version you have The more appropriate ones have the option to fork a subprocess for each new incoming connection)
Note that i'm on a 32b windows7, for 64bit use nc64.exe Test by typing hello in one command window and check if it is displayed in the other. There might be a cleaner combination of options that avoids the need for the /dev/null but i couldn't figure out what. I'm trying to do a custom dockerfile with jenkins on it I would to wait until port 8080 is open instead of doing an ugly 'sleep 60' with netcat but i'm not very confident with bash scripts and net. The old nc version doesn't allow using different usernames for the bastion and target server
WATCH
