# in environment ?
by lejeczek
Hi guys.
Do you use # in your envs?
I wonder if it's just me having issues with those.
For a test, to reproduce the issue, 'ghost' web solution
would be easy & quick:
-> $ podman run -dt ...................... --env
database__client=mysql --env
database__connection__host=11.1.0.1 --env
database__connection__user=ghostadm --env
database__connection__password='xyz#admghost' --env
database__connection__database=ghost_xyz --env
url=https://ghost.xyz
So far all I've tried with 'database__connection__password'
failed, quoting &| escaping.
I often use # - does anybody have a way to make it work?
many thanks, L.
2 months
RunRoot & mistaken IDs
by lejeczek
Hi guys.
I experience this:
-> $ podman images
WARN[0000] RunRoot is pointing to a path
(/run/user/1007/containers) which is not writable. Most
likely podman will fail.
Error: creating events dirs: mkdir /run/user/1007:
permission denied
-> $ id
uid=2001(podmania) gid=2001(podmania) groups=2001(podmania)
context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
I think it might have something to do with the fact that I
changed UID for the user, but why would this be?
How troubleshoot & fix it, ideally without system reboot?
many thanks, L.
3 months, 1 week
shouldn't the current directory be the default context for "podman build"?
by Robert P. J. Day
"man podman-build" suggests that the context argument is optional:
SYNOPSIS
podman build [options] [context]
podman image build [options] [context]
...
If no context directory is specified, then Podman will assume
the current working directory as the build context, which
should contain the Containerfile.
but if i have a directory with nothing but a Containerfile, i get:
$ podman build
Error: no context directory specified, and no containerfile specified
$
OTOH, specifying context of current directory:
$ podman build .
STEP 1: FROM alpine:latest
... etc etc ...
thoughts?
rday
10 months
Podman v5.2.3 Released
by Do Not Reply
Hi all,
Podman v5.2.3 is now available. You may view the full details at
https://github.com/containers/podman/releases/tag/v5.2.3
Release Notes:
--------------
### Bugfixes
- Fixed a bug that could cause network namespaces to fail to unmount, resulting in Podman commands hanging.
- Fixed a bug where Podman could not run images which included SCTP exposed ports.
- Fixed a bug where containers run by the root user, but inside a user namespace (including inside a container), could not use the `pasta` network mode.
- Fixed a bug where volume copy-up did not properly chown empty volumes when the `:idmap` mount option was used.
### Misc
- Updated Buildah to v1.37.3
This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.
1 year
(no subject)
by Larry Cai
Hi:
I have podman-remote / podman server deployment inside one kubernetes,
podman build works, but when I execute podman run, it reports error
Any suggestions for the direction?
```
jovyan@workenv-0:~$ podman version
Client: Podman Engine
Version: 5.2.2
API Version: 5.2.2
Go Version: go1.23.0
Git Commit: fcee48106a12dd531702d729d17f40f6e152027f
Built: Wed Aug 21 20:01:29 2024
OS/Arch: linux/amd64
Server: Podman Engine
Version: 4.9.4-rhel
API Version: 4.9.4-rhel
Go Version: go1.21.11 (Red Hat 1.21.11-1.el9_4)
Built: Mon Jul 1 10:27:14 2024
OS/Arch: linux/amd64
jovyan@workenv-0:~$ podman run --log-level debug hello-world
INFO[0000] podman filtering at log level debug
DEBU[0000] Called run.PersistentPreRunE(podman run --log-level debug
hello-world)
DEBU[0000] DoRequest Method: GET URI: http://d/v5.2.2/libpod/_ping
DEBU[0000] Loading registries configuration
"/etc/containers/registries.conf"
DEBU[0000] DoRequest Method: POST URI: http://d/v5.2.2/libpod/images/pull
DEBU[0000] DoRequest Method: GET URI:
http://d/v5.2.2/libpod/images/hello-world/json
DEBU[0000] DoRequest Method: POST URI:
http://d/v5.2.2/libpod/containers/create
DEBU[0000] Enabling signal proxying
DEBU[0000] Enabling signal proxying
DEBU[0000] DoRequest Method: GET URI:
http://d/v5.2.2/libpod/containers/015c01ec8bf0ec94ce7a7864b3dfdcf1c996365...
DEBU[0000] DoRequest Method: POST URI:
http://d/v5.2.2/libpod/containers/015c01ec8bf0ec94ce7a7864b3dfdcf1c996365...
DEBU[0000] ExitCode msg: "unmarshalling error into
&errorhandling.errormodel{because:\"\", message:\"\", responsecode:0}, data
\"\": unexpected end of json input"
Error: unmarshalling error into &errorhandling.ErrorModel{Because:"",
Message:"", ResponseCode:0}, data "": unexpected end of JSON input
DEBU[0000] Shutting down engines
````
* podman server is based on ubi9/podman with start script for "podman
system service --time=0 tcp:[::]:12375"
* downgrade podman client to 4.9.9 doesn't give any help
Rgs/Larry
1 year, 1 month
