stage1: fix socket activation port matching
stage1: fix socket activation port matching

We were using the pod's port to set up the socket unit file inside the
pod. This means it only worked if the port in the image manifest and the
port in the pod manifest (set by rkt at runtime) were the same.

The reason is that systemd inside the host matches based on the socket
port number, and since the socket is created on the host, it will have
the host port number. If this number is different from the one in the
image manifest, systemd will not assign the socket to the correct app in
the pod because it will expect a socket with the image manifest port
number.

The solution is using the host port number for the socket unit file.

akshaykarle/rkt,shobhit85/rkt,Shashwatsh/rkt,squeed/rkt,squeed/rkt,ybubnov/rkt,lucasallan/rkt,monstermunchkin/rkt,squeed/rkt,il9ue/rkt,sgotti/rkt,matthaias/rkt,nhlfr/rkt,sgotti/rkt,shobhit85/rkt,yifan-gu/rkt,kinvolk/rkt,yifan-gu/rocket,coreos/rkt,rkt/rkt,mike1729/rkt,alban/rkt,jjlakis/rkt,sstabellini/rkt,lucasallan/rkt,ybubnov/rkt,akshaykarle/rkt,rkt/rkt,tmrts/rkt,intelsdi-x/rkt,monstermunchkin/rkt,joshix/rkt,kinvolk/rkt,jakon89/rkt,achanda/rkt,shobhit85/rkt,markllama/rkt,nhlfr/rkt,ybubnov/rkt,dgonyeo/rkt,achanda/rkt,Wilybald/rkt,lucasallan/rkt,yifan-gu/rocket,yifan-gu/rocket,lucasallan/rkt,Shashwatsh/rkt,euank/rkt,tmrts/rkt,tmrts/rkt,joshix/rkt,mike1729/rkt,dgonyeo/rkt,nhlfr/rkt,markllama/rkt,rkt/rkt,dgonyeo/rkt,intelsdi-x/rkt,Shashwatsh/rkt,alban/rkt,jjlakis/rkt,jjlakis/rkt,euank/rkt,Wilybald/rkt,joshix/rkt,sstabellini/rkt,akshaykarle/rkt,jonboulle/rkt,cab105/rkt,s-urbaniak/rkt,monstermunchkin/rkt,markllama/rkt,jakon89/rkt,s-urbaniak/rkt,coreos/rkt,yifan-gu/rkt,il9ue/rkt,il9ue/rkt,kinvolk/rkt,matthaias/rkt,cab105/rkt,sgotti/rkt,sstabellini/rkt,euank/rkt,matthaias/rkt,kinvolk/rkt,jakon89/rkt,achanda/rkt,s-urbaniak/rkt,mike1729/rkt,jonboulle/rkt,intelsdi-x/rkt,yifan-gu/rkt,Wilybald/rkt,joshix/rkt,alban/rkt,rkt/rkt,cab105/rkt,Wilybald/rkt,coreos/rkt,jonboulle/rkt