First of all, I must say how much I hated the transition from hub.docker.com to icr. You go to icr.io you are redirect to a sales page for container registry! Huh!!!

Anyway.. I don't want to diverge that discussion from my real issue:

if I run the image without specifying the -v for the data in Podman, it is not possible to connect to the database. and Everything works just fine in docker.

I need just a quick DB to run my unit tests so I don't really need persistence.

It's a bit worse to me as it does not work in MAC if I specify the -v..

So I'm on a weird situation, that if I'm on Mac I must use docker and not map a folder, but if I'm on Linux I have to either use docker or -v to a volume.

I am collecting scripts for my unit-tests here: 

https://github.com/clebertsuconic/activemq-artemis/tree/more-databases/tests/database-support/scripts

(I don't think the link will survive after a few weeks, but I will have moved it somewhere in artemis if you are reading this from a near future).

I discovered the same phenomena yesterday on RHEL9/Fedora 38. If I don't specify -v for /database db2 does not start. I tried adding:

 -e PERSISTENT_HOME=false

and then it seems to work. The documentation at: https://hub.docker.com/r/ibmcom/db2/ says:

 PERSISTENT_HOME is true by default, only specify to false if you are running Docker for Windows.

which is a bit confusing

First of all, I must say how much I hated the transition from hub.docker.com to icr. You go to icr.io you are redirect to a sales page for container registry! Huh!!!

Anyway.. I don't want to diverge that discussion from my real issue:

if I run the image without specifying the -v for the data in Podman, it is not possible to connect to the database. and Everything works just fine in docker.

I need just a quick DB to run my unit tests so I don't really need persistence.

It's a bit worse to me as it does not work in MAC if I specify the -v..

So I'm on a weird situation, that if I'm on Mac I must use docker and not map a folder, but if I'm on Linux I have to either use docker or -v to a volume.

I am collecting scripts for my unit-tests here: 

https://github.com/clebertsuconic/activemq-artemis/tree/more-databases/tests/database-support/scripts

(I don't think the link will survive after a few weeks, but I will have moved it somewhere in artemis if you are reading this from a near future).

Thank you so much... that did the trick. It's all working now:

It is currently sitting on this repo:

https://github.com/clebertsuconic/activemq-artemis/tree/more-databases/tests/db-tests/scripts

and I will be under here in a couple weeks:

https://github.com/apache/activemq-artemis/tree/main/tests/db-tests/scripts

I discovered the same phenomena yesterday on RHEL9/Fedora 38. If I don't specify -v for /database db2 does not start. I tried adding:

 -e PERSISTENT_HOME=false

and then it seems to work. The documentation at: https://hub.docker.com/r/ibmcom/db2/ says:

 PERSISTENT_HOME is true by default, only specify to false if you are running Docker for Windows.

which is a bit confusing

First of all, I must say how much I hated the transition from hub.docker.com to icr. You go to icr.io you are redirect to a sales page for container registry! Huh!!!

Anyway.. I don't want to diverge that discussion from my real issue:

if I run the image without specifying the -v for the data in Podman, it is not possible to connect to the database. and Everything works just fine in docker.

I need just a quick DB to run my unit tests so I don't really need persistence.

It's a bit worse to me as it does not work in MAC if I specify the -v..

So I'm on a weird situation, that if I'm on Mac I must use docker and not map a folder, but if I'm on Linux I have to either use docker or -v to a volume.

I am collecting scripts for my unit-tests here: 

https://github.com/clebertsuconic/activemq-artemis/tree/more-databases/tests/database-support/scripts

(I don't think the link will survive after a few weeks, but I will have moved it somewhere in artemis if you are reading this from a near future).

Actually.. something still going on...

it worked on mac, but it failed on Linux.

It always work with docker.

how can I raise an issue? there's no JIRA, nothing?

Thank you so much... that did the trick. It's all working now:

It is currently sitting on this repo:

https://github.com/clebertsuconic/activemq-artemis/tree/more-databases/tests/db-tests/scripts

and I will be under here in a couple weeks:

https://github.com/apache/activemq-artemis/tree/main/tests/db-tests/scripts

I discovered the same phenomena yesterday on RHEL9/Fedora 38. If I don't specify -v for /database db2 does not start. I tried adding:

 -e PERSISTENT_HOME=false

and then it seems to work. The documentation at: https://hub.docker.com/r/ibmcom/db2/ says:

 PERSISTENT_HOME is true by default, only specify to false if you are running Docker for Windows.

which is a bit confusing

First of all, I must say how much I hated the transition from hub.docker.com to icr. You go to icr.io you are redirect to a sales page for container registry! Huh!!!

Anyway.. I don't want to diverge that discussion from my real issue:

if I run the image without specifying the -v for the data in Podman, it is not possible to connect to the database. and Everything works just fine in docker.

I need just a quick DB to run my unit tests so I don't really need persistence.

It's a bit worse to me as it does not work in MAC if I specify the -v..

So I'm on a weird situation, that if I'm on Mac I must use docker and not map a folder, but if I'm on Linux I have to either use docker or -v to a volume.

I am collecting scripts for my unit-tests here: 

https://github.com/clebertsuconic/activemq-artemis/tree/more-databases/tests/database-support/scripts

(I don't think the link will survive after a few weeks, but I will have moved it somewhere in artemis if you are reading this from a near future).

Actually.. something still going on...

it worked on mac, but it failed on Linux.

It always work with docker.

how can I raise an issue? there's no JIRA, nothing?

Thank you so much... that did the trick. It's all working now:

It is currently sitting on this repo:

https://github.com/clebertsuconic/activemq-artemis/tree/more-databases/tests/db-tests/scripts

and I will be under here in a couple weeks:

https://github.com/apache/activemq-artemis/tree/main/tests/db-tests/scripts

I discovered the same phenomena yesterday on RHEL9/Fedora 38. If I don't specify -v for /database db2 does not start. I tried adding:

 -e PERSISTENT_HOME=false

and then it seems to work. The documentation at: https://hub.docker.com/r/ibmcom/db2/ says:

 PERSISTENT_HOME is true by default, only specify to false if you are running Docker for Windows.

which is a bit confusing

First of all, I must say how much I hated the transition from hub.docker.com to icr. You go to icr.io you are redirect to a sales page for container registry! Huh!!!

Anyway.. I don't want to diverge that discussion from my real issue:

if I run the image without specifying the -v for the data in Podman, it is not possible to connect to the database. and Everything works just fine in docker.

I need just a quick DB to run my unit tests so I don't really need persistence.

It's a bit worse to me as it does not work in MAC if I specify the -v..

So I'm on a weird situation, that if I'm on Mac I must use docker and not map a folder, but if I'm on Linux I have to either use docker or -v to a volume.

I am collecting scripts for my unit-tests here: 

https://github.com/clebertsuconic/activemq-artemis/tree/more-databases/tests/database-support/scripts

(I don't think the link will survive after a few weeks, but I will have moved it somewhere in artemis if you are reading this from a near future).

I'm not really sure what to look for

the project is at

git clone https://github.com/clebertsuconic/activemq-artemis.git

git checkout more-databases

cd tests/db-tests/scripts

./start-db2.sh

There seems to be an error message at the end with podman logs -f db2-artemis-test:

But the fact it runs on docker and not on podman tells me that there's an issue with the image itself. I was wondering how I could raise an issue with ibm on the image. 

Actually.. something still going on...

it worked on mac, but it failed on Linux.

It always work with docker.

how can I raise an issue? there's no JIRA, nothing?

Thank you so much... that did the trick. It's all working now:

It is currently sitting on this repo:

https://github.com/clebertsuconic/activemq-artemis/tree/more-databases/tests/db-tests/scripts

and I will be under here in a couple weeks:

https://github.com/apache/activemq-artemis/tree/main/tests/db-tests/scripts

I discovered the same phenomena yesterday on RHEL9/Fedora 38. If I don't specify -v for /database db2 does not start. I tried adding:

 -e PERSISTENT_HOME=false

and then it seems to work. The documentation at: https://hub.docker.com/r/ibmcom/db2/ says:

 PERSISTENT_HOME is true by default, only specify to false if you are running Docker for Windows.

which is a bit confusing

First of all, I must say how much I hated the transition from hub.docker.com to icr. You go to icr.io you are redirect to a sales page for container registry! Huh!!!

Anyway.. I don't want to diverge that discussion from my real issue:

if I run the image without specifying the -v for the data in Podman, it is not possible to connect to the database. and Everything works just fine in docker.

I need just a quick DB to run my unit tests so I don't really need persistence.

It's a bit worse to me as it does not work in MAC if I specify the -v..

So I'm on a weird situation, that if I'm on Mac I must use docker and not map a folder, but if I'm on Linux I have to either use docker or -v to a volume.

I am collecting scripts for my unit-tests here: 

https://github.com/clebertsuconic/activemq-artemis/tree/more-databases/tests/database-support/scripts

(I don't think the link will survive after a few weeks, but I will have moved it somewhere in artemis if you are reading this from a near future).

Actually.. something still going on...

it worked on mac, but it failed on Linux.

It always work with docker.

how can I raise an issue? there's no JIRA, nothing?

Thank you so much... that did the trick. It's all working now:

It is currently sitting on this repo:

https://github.com/clebertsuconic/activemq-artemis/tree/more-databases/tests/db-tests/scripts

and I will be under here in a couple weeks:

https://github.com/apache/activemq-artemis/tree/main/tests/db-tests/scripts

I discovered the same phenomena yesterday on RHEL9/Fedora 38. If I don't specify -v for /database db2 does not start. I tried adding:

 -e PERSISTENT_HOME=false

and then it seems to work. The documentation at: https://hub.docker.com/r/ibmcom/db2/ says:

 PERSISTENT_HOME is true by default, only specify to false if you are running Docker for Windows.

which is a bit confusing

First of all, I must say how much I hated the transition from hub.docker.com to icr. You go to icr.io you are redirect to a sales page for container registry! Huh!!!

Anyway.. I don't want to diverge that discussion from my real issue:

if I run the image without specifying the -v for the data in Podman, it is not possible to connect to the database. and Everything works just fine in docker.

I need just a quick DB to run my unit tests so I don't really need persistence.

It's a bit worse to me as it does not work in MAC if I specify the -v..

So I'm on a weird situation, that if I'm on Mac I must use docker and not map a folder, but if I'm on Linux I have to either use docker or -v to a volume.

I am collecting scripts for my unit-tests here: 

https://github.com/clebertsuconic/activemq-artemis/tree/more-databases/tests/database-support/scripts

(I don't think the link will survive after a few weeks, but I will have moved it somewhere in artemis if you are reading this from a near future).

Actually.. it's working...

it's just that it had a false start once.. retried it and worked.

Thank you so much for your help

Actually.. something still going on...

it worked on mac, but it failed on Linux.

It always work with docker.

how can I raise an issue? there's no JIRA, nothing?

Thank you so much... that did the trick. It's all working now:

It is currently sitting on this repo:

https://github.com/clebertsuconic/activemq-artemis/tree/more-databases/tests/db-tests/scripts

and I will be under here in a couple weeks:

https://github.com/apache/activemq-artemis/tree/main/tests/db-tests/scripts

I discovered the same phenomena yesterday on RHEL9/Fedora 38. If I don't specify -v for /database db2 does not start. I tried adding:

 -e PERSISTENT_HOME=false

and then it seems to work. The documentation at: https://hub.docker.com/r/ibmcom/db2/ says:

 PERSISTENT_HOME is true by default, only specify to false if you are running Docker for Windows.

which is a bit confusing

First of all, I must say how much I hated the transition from hub.docker.com to icr. You go to icr.io you are redirect to a sales page for container registry! Huh!!!

Anyway.. I don't want to diverge that discussion from my real issue:

if I run the image without specifying the -v for the data in Podman, it is not possible to connect to the database. and Everything works just fine in docker.

I need just a quick DB to run my unit tests so I don't really need persistence.

It's a bit worse to me as it does not work in MAC if I specify the -v..

So I'm on a weird situation, that if I'm on Mac I must use docker and not map a folder, but if I'm on Linux I have to either use docker or -v to a volume.

I am collecting scripts for my unit-tests here: 

https://github.com/clebertsuconic/activemq-artemis/tree/more-databases/tests/database-support/scripts

(I don't think the link will survive after a few weeks, but I will have moved it somewhere in artemis if you are reading this from a near future).