Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kpod run -p .. does not bind the ports #129

Closed
surajssd opened this issue Dec 13, 2017 · 5 comments
Closed

kpod run -p .. does not bind the ports #129

surajssd opened this issue Dec 13, 2017 · 5 comments
Assignees
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@surajssd
Copy link
Contributor

Type

/kind bug

What is happening

I am trying to do port binding on my machine from container, but kpod does not bind the ports. Also kpod ps does not show the port information. When curled on the endpoint it fails obviously since the port is not bound.

Steps to reproduce:

# kpod run -d -p 8000:8000 centos python -m SimpleHTTPServer                             
Trying to pull ...Trying to pull docker.io/library/centos:latest...                            
Getting image source signatures                
Copying blob sha256:85432449fd0fabb6bef4772246d9b7948723275a4c7e4dee18728f28d79f1c2c           
 70.03 MB / 70.03 MB [=====================================================] 17s               
Copying config sha256:3fa822599e10c5f2080dcf647068c72022b111d31bbec0c5adb8a96e7eb5379b         
 1.82 KB / 1.82 KB [========================================================] 0s               
Writing manifest to image destination          
Storing signatures                             
ad60539f9cd3a6a29601ec1467c834ae554e6e07d5d6a9de6b67adbf78a43550                               

# kpod ps
CONTAINER ID   IMAGE                     COMMAND                      CREATED AT       STATUS              PORTS   NAMES
ad60539f9cd3   docker.io/centos:latest   python -m SimpleHTTPServer   11 seconds ago   Up 11 seconds ago           elated_hugle

# curl localhost:8000
curl: (7) Failed to connect to localhost port 8000: Connection refused

Versions:

# kpod version
Version:       0.1
Go Version:    go1.9.2
Git Commit:    "e456c07813c5ccc6ccc81ad9a103e46e1b59b50c"
Built:         Wed Dec 13 15:48:19 2017
OS/Arch:       linux/amd64

# runc -v
runc version 1.0.0-rc4+dev
commit: 97b8bfe7fdea74d5e49b657013455a888328f04e
spec: 1.0.0

# rpm -aq | grep runc
runc-1.0.0-12.rc4.gitaea4f21.fc27.x86_64

# cat /etc/os-release 
NAME=Fedora
VERSION="27 (Cloud Edition)"
ID=fedora
VERSION_ID=27
PRETTY_NAME="Fedora 27 (Cloud Edition)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:27"
HOME_URL="https://fedoraproject.org/"
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=27
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=27
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Cloud Edition"
VARIANT_ID=cloud

# getenforce 
Enforcing
@mheon
Copy link
Member

mheon commented Dec 13, 2017

Networking support is still WIP - see #109
Hopefully will be ready soon, though

@surajssd
Copy link
Contributor Author

@mheon I am trying to write tests for #75

For that to run I am trying to setup registry but then for it to work, I am trying to bind the local registry to machine's 5000 port which is not working and hence reported this. Not sure how do I proceed with tests for #75 ? Any suggestions?

@anarcat
Copy link
Contributor

anarcat commented Dec 15, 2017

just FWIW, #109 was merged and the next step is #142, which "Enable host and bridge communications". see also #109 (comment)

@mheon
Copy link
Member

mheon commented Jan 10, 2018

@baude is working on this now

@baude
Copy link
Member

baude commented Jan 22, 2018

this should be working on master now, re-open if not

@baude baude closed this as completed Jan 22, 2018
baude pushed a commit to baude/podman that referenced this issue Aug 31, 2019
…eakage_bridge

bridge: release IP in case of error
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

4 participants