Open PlatonB opened 1 year ago
Can the user running Podman access the journal (simple check is to run journalctl
; if it doesn't error and you get log output, then the user has access).
journalctl
сен 02 20:02:29 localhost kernel: Linux version 5.19.17 (tomjon@buildstream) (gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.38) #1 SMP PREEMPT_DYNAMIC Thu Nov 10 15:00:00 UTC 2011
сен 02 20:02:29 localhost kernel: Command line: initrd=\ostree\gnome-os-a48ee442a9a85236aafd59af80ceb1b50fe9fd474c08c8f2b2d55c016d3f1d41\initramfs-5.19.17.img rw quiet splash console=tty0 ostree=/ostree/boot.0/gnome-os/a48ee442a9a85236aa>
...
Two things:
podman events
in a separate terminal before running podman exec
and see what events appear?podman exec
and see if Podman added any logs?podman events
endlessly repeats this strings output:
2023-09-20 10:15:44.651305503 +0300 MSK container init 89e2ce9aa76c5f822adc1fa66c01198281a3cc037518b20c33aa0277466aa1d7 (image=docker.io/mongodb/mongodb-community-server:latest, name=mongodb, maintainer=support@mongodb.com, name=MongoDB Standalone, org.opencontainers.image.ref.name=ubuntu, org.opencontainers.image.version=22.04, summary=MongoDB Standalone Container, vendor=MongoDB, version=7.0.1, description=Container configured with a standalone instance of MongoDB)
2023-09-20 10:15:44.658146379 +0300 MSK container start 89e2ce9aa76c5f822adc1fa66c01198281a3cc037518b20c33aa0277466aa1d7 (image=docker.io/mongodb/mongodb-community-server:latest, name=mongodb, summary=MongoDB Standalone Container, vendor=MongoDB, version=7.0.1, description=Container configured with a standalone instance of MongoDB, maintainer=support@mongodb.com, name=MongoDB Standalone, org.opencontainers.image.ref.name=ubuntu, org.opencontainers.image.version=22.04)
2023-09-20 10:15:44.830002278 +0300 MSK container died 89e2ce9aa76c5f822adc1fa66c01198281a3cc037518b20c33aa0277466aa1d7 (image=docker.io/mongodb/mongodb-community-server:latest, name=mongodb, name=MongoDB Standalone, org.opencontainers.image.ref.name=ubuntu, org.opencontainers.image.version=22.04, summary=MongoDB Standalone Container, vendor=MongoDB, version=7.0.1, description=Container configured with a standalone instance of MongoDB, maintainer=support@mongodb.com)
2023-09-20 10:15:44.848983499 +0300 MSK container restart 89e2ce9aa76c5f822adc1fa66c01198281a3cc037518b20c33aa0277466aa1d7 (image=docker.io/mongodb/mongodb-community-server:latest, name=mongodb, maintainer=support@mongodb.com, name=MongoDB Standalone, org.opencontainers.image.ref.name=ubuntu, org.opencontainers.image.version=22.04, summary=MongoDB Standalone Container, vendor=MongoDB, version=7.0.1, description=Container configured with a standalone instance of MongoDB)
Attempting to run podman exec
:
podman exec
Error: exec requires the name or ID of a container or the --latest flag
podman exec mongodb
Error: must provide a non-empty command to start an exec session: invalid argument
podman exec 89e2ce9aa76c
Error: must provide a non-empty command to start an exec session: invalid argument
podman exec --latest
Error: must provide a non-empty command to start an exec session: invalid argument
A friendly reminder that this issue had no activity for 30 days.
@mheon @PlatonB Is this still an issue?
The event is definitely there (we can see it in podman events
) so it's very interesting that podman exec
can't find it. Would need to be able to reproduce to debug much further, and I can't make this happen on my system. Possibly a journal configuration issue?
Though - that podman events
trace is only container events, not exec events, so a trace after a successful podman exec
into the container would be more enlightening.
@mheon @PlatonB Is this still an issue?
@rhatdan Yes(. The Podman version is more recent (4.7.1), but Mongodb Shell still doesn't run.
Would need to be able to reproduce to debug much further, and I can't make this happen on my system.
@mheon Have you tried it specifically on the devel branch of Gnome OS 45?
Issue Description
GNOME OS Development (45) podman version 4.6.2
Steps to reproduce the issue
Describe the results you received
See "Steps to reproduce the issue"
Describe the results you expected
Normally, the
podman exec -it mongodb mongosh
command should open the MongoDB shell.podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Gnome Boxes (flatpak)
Additional information