# 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 weeks, 6 days
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.
1 month, 3 weeks
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
8 months, 2 weeks
image platform (linux/amd64) does not match expected platform (linux/linux/arm64)
by Mehdi Haghgoo
Hi all,
I'm trying to run rabbitmq images on MacBook M1 and I see warnings like:
WARNING: image platform (linux/amd64) does not match the expected platform (linux/linux/arm64)
I run the command:
podman run --rm -p 8000:8080 --arch linux/arm64 ghcr.io/code-with-mehdi/rabbitmq:3-management
and it fails to boot with a lot of logs that I like below:
Mozilla Community Pastebin/QTExU80S (Plain Text)
Mozilla Community Pastebin/QTExU80S (Plain Text)
Is there a special flag I need to pass to fetch arm64 images?
I'm not sure the boot issue has anything to do with the image arch incompatibility, though. Some enlightening on this from someone who has experience and insight will be appreciated.
Best regards,
Mehdi
1 year, 2 months
Fly containers on the fly using podman YAML
by Mehdi Haghgoo
I have problem running docker-compose on a Rocky Linux server 9.4. Instead of Docker Compose, I want to use Podman. A service in my compose.yaml file creates a container on the fly using Containerfile and runs the service.
When running an container equivalent to this service, how can I create the container on the fly by first building using the Containerfile and then bringing up the service?
Is this possible?
Or should I first create a custom image, push it to repo and pull it before running the container?
1 year, 2 months
