-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Podman not starting oracle enterprise container #11903
Comments
Can you provide a reproducer that doesn't use podman-compose? |
Hello. $ podman-compose up |
It looks like podman successfully starts the container. This looks like an configuration error. Can you inspect the container and provide the output please. |
@Luap99, i have attached few files for comparison. Please follow the names as descriptions. Regards and thank you. |
Attaching docker-compose file. |
@kbul Thanks, this is helpful. Could also inspect the infra container of the pod. You can get the infra container ID with |
@Luap99, attaching two files just in case (executed commands inside the fil) |
@Luap99, if any more information is needed, or the one i provided is not sufficient, do not hesitate to let me know. Regards. |
OK I cannot find something wrong in the inspect output. How do you connect to the db, from the host via port forwarding or from another container within the pod? |
I have left the container startup for a longer time, attaching command output Please observe time stamps. There is a situation in which after 10 minutes it started to do some work. I was not that patience before. But still no luck in connecting to the database. |
I am connecting from host using SQL-Developer from Oracle with the following configuration: That configuration works with the older version of podman. |
Another observation that i think is worth to share.
Result. I am able to connect to the DB. |
Sorry for the delay. The inspect output looks correct. Can you compare the /etc/hosts content in the container between the old and new version. This might be related to this issue #12003. |
Hello. $ podman version sh-4.2$ cat /etc/hosts used by slirp4netns10.0.2.100 oracle 1abb44ab84d9-infra $ podman version sh-4.2$ cat /etc/hosts used by slirp4netns10.0.2.100 oracle 2b314aade7bc-infra |
$ podman version sh-4.2$ cat /etc/hosts used by slirp4netns10.0.2.100 oracle 1abb44ab84d9-infra $ podman version sh-4.2$ cat /etc/hosts used by slirp4netns10.0.2.100 oracle 2b314aade7bc-infra |
Sorry i accidentally pressed the close issue button. |
A friendly reminder that this issue had no activity for 30 days. |
@kbul is this still broken? |
Good day @rhatdan, |
@Luap99 any more thoughts? |
Recently we were discussing an option in which /etc/hosts entries changed. Would it work if i add those entries manually and restart the container (not recreate the image, but podman start previously running container)? |
Try it out, that should help. |
A friendly reminder that this issue had no activity for 30 days. |
Hello. Recent update to version 3.4.4 still does not solve the problem. Regards. |
Hello. It started work again. Not sure how it happened. I did not configure anything specific. Anyway, thank you for handling the issue. |
Is this a BUG REPORT? (leave only one on its own line)
/kind bug
When executoing the following command:
$ podman-compose up
using podman version: podman version 3.4.0
podman pod create --name=oracle --share net -p 5503:5500 -p 1521:1521
45ad43454fa8238272bb5f64e6fe5795c6de23650ec37491d2e77982ac652c4f
One cannot connect to the DB by means of for example DBEAVER client.
It stucks (providing no error) at some point of container instantiation. Attempting to connect to the database gives the following error.
Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
Downgrading to version 3.1.0, and executing the following:
$ podman-compose up
using podman version: podman version 3.1.0
podman pod create --name=oracle --share net -p 5503:5500 -p 1521:1521
298a4e3c427a00c7a83fd84746dba73c1a9893d6dc68a2e37be252c7f54364a9
Works fine.
Url to oracle docker image: https://hub.docker.com/_/oracle-database-enterprise-edition
Steps to reproduce the issue:
Describe the results you received:
Not able to connect to the database.
Describe the results you expected:
Database connection.
Additional information you deem important (e.g. issue happens only occasionally):
Issue permanent.
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Host running Fedora.
The text was updated successfully, but these errors were encountered: