Replies: 4 comments 2 replies
|
This is a podman-compose question, which is a different project then podman. |
0 replies
|
No, it's def podman (or I guess it could be the container). I also get the same results with a straight up podman command: |
0 replies
|
Same error if I run it with the |
2 replies
|
inside the same folder i did just below steap and work it from me |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'm new to podman, and I'm having an awful time getting a mysql container to run. I managed to get my php-fpm and nginx containers working and serving files, but mysql keeps erroring out . I've pared back everything to the barest bones and still get the same error.
I'm on Ubuntu 22 and am using podman compose to set stuff up. My compose.yml file is down to:
I run
podman-compose upand I get:I always get that error about
/var/lib/mysql/already existing, which makes no sense to me. I assume that is a path inside the container so I don't get how it would be an issue.I ended up making a new user on my computer and this all worked once... but then... somehow it stopped working again.
It does seem a little weird to me that
Entrypoint script for MySQL Server 8.2.0-1.el8 started.shows up twice in the output...All reactions