castillofrancodamian
commented
1 year ago Open castillofrancodamian opened 1 year ago
castillofrancodamian
commented
1 year ago 
aparcar
commented
1 year ago asu on main [$?] is 📦 v0.0.0 via 🐍 v3.11.3 on ☁️ mail@aparcar.org
❯ podman-compose up
['podman', '--version', '']
using podman version: 4.5.0
** excluding: set()
['podman', 'inspect', '-t', 'image', '-f', '{{.Id}}', 'localhost/aparcar/asu:latest']
['podman', 'inspect', '-t', 'image', '-f', '{{.Id}}', 'localhost/aparcar/asu:latest']
['podman', 'inspect', '-t', 'image', '-f', '{{.Id}}', 'localhost/aparcar/asu:latest']
podman volume inspect asu_podman-sock || podman volume create asu_podman-sock
['podman', 'volume', 'inspect', 'asu_podman-sock']
['podman', 'network', 'exists', 'asu_default']
podman create --name=asu_podman_1 --label io.podman.compose.config-hash=123 --label io.podman.compose.project=asu --label io.podman.compose.version=0.0.1 --label com.docker.compose.project=asu --label com.docker.compose.project.working_dir=/Users/user/src/openwrt/asu --label com.docker.compose.project.config_files=podman-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=podman -v asu_podman-sock:/tmp/socket/ --net asu_default --network-alias podman -u podman quay.io/podman/stable sh -c mkdir -p /tmp/socket && podman system service --time=0 unix:///tmp/socket/podman.sock
Error: creating container storage: the container name "asu_podman_1" is already in use by fa885946636392fe0c7b577532c23b23a4dfccefe0d1c846addc15b5241c61e5. You have to remove that container to be able to reuse that name: that name is already in use
exit code: 125
podman volume inspect asu_redis || podman volume create asu_redis
['podman', 'volume', 'inspect', 'asu_redis']
['podman', 'network', 'exists', 'asu_default']
podman create --name=asu_redis_1 --label io.podman.compose.config-hash=123 --label io.podman.compose.project=asu --label io.podman.compose.version=0.0.1 --label com.docker.compose.project=asu --label com.docker.compose.project.working_dir=/Users/user/src/openwrt/asu --label com.docker.compose.project.config_files=podman-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=redis -v asu_redis:/data/:rw --net asu_default --network-alias redis docker.io/redis:alpine
Error: creating container storage: the container name "asu_redis_1" is already in use by 3d2bd1a1eea834b7e264218598887a33de4bc4676ab76f5642f1196cec5f02a9. You have to remove that container to be able to reuse that name: that name is already in use
exit code: 125
['podman', 'network', 'exists', 'asu_default']
podman create --name=asu_server_1 --label io.podman.compose.config-hash=123 --label io.podman.compose.project=asu --label io.podman.compose.version=0.0.1 --label com.docker.compose.project=asu --label com.docker.compose.project.working_dir=/Users/user/src/openwrt/asu --label com.docker.compose.project.config_files=podman-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=server -e REDIS_URL=redis://redis/ -v /Users/user/src/openwrt/asu/asu-service/public:/app/public/:rw --net asu_default --network-alias server -p 127.0.0.1:8000:8000 localhost/aparcar/asu:latest
Error: creating container storage: the container name "asu_server_1" is already in use by 92c7401b590f27661991d94c2125746a6ce0bdc00fc526e2a03dd546b69a8583. You have to remove that container to be able to reuse that name: that name is already in use
exit code: 125
podman volume inspect asu_podman-sock || podman volume create asu_podman-sock
['podman', 'volume', 'inspect', 'asu_podman-sock']
['podman', 'network', 'exists', 'asu_default']
podman create --name=asu_worker_1 --label io.podman.compose.config-hash=123 --label io.podman.compose.project=asu --label io.podman.compose.version=0.0.1 --label com.docker.compose.project=asu --label com.docker.compose.project.working_dir=/Users/user/src/openwrt/asu --label com.docker.compose.project.config_files=podman-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=worker -e CONTAINER_HOST=unix:///tmp/socket/podman.sock -e REDIS_URL=redis://redis/ -v /Users/user/src/openwrt/asu/asu-service/public:/app/public/:rw -v asu_podman-sock:/tmp/socket/:rw --net asu_default --network-alias worker localhost/aparcar/asu:latest rqworker --url redis://redis
Error: creating container storage: the container name "asu_worker_1" is already in use by fbd05219ed9b6752b493828b9997038eb1c91307a47b8c58aa3ef81381d48f21. You have to remove that container to be able to reuse that name: that name is already in use
exit code: 125
podman volume inspect asu_podman-sock || podman volume create asu_podman-sock
['podman', 'volume', 'inspect', 'asu_podman-sock']
['podman', 'network', 'exists', 'asu_default']
podman create --name=asu_worker2_1 --label io.podman.compose.config-hash=123 --label io.podman.compose.project=asu --label io.podman.compose.version=0.0.1 --label com.docker.compose.project=asu --label com.docker.compose.project.working_dir=/Users/user/src/openwrt/asu --label com.docker.compose.project.config_files=podman-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=worker2 -e CONTAINER_HOST=unix:///tmp/socket/podman.sock -e REDIS_URL=redis://redis/ -v /Users/user/src/openwrt/asu/asu-service/public:/app/public/:rw -v asu_podman-sock:/tmp/socket/:rw --net asu_default --network-alias worker2 localhost/aparcar/asu:latest rqworker --url redis://redis
Error: creating container storage: the container name "asu_worker2_1" is already in use by 5ea68c5a794599862e65552fceb64c3a6c751482bd1028c32898b8b751bdc749. You have to remove that container to be able to reuse that name: that name is already in use
exit code: 125
podman start -a asu_podman_1
podman start -a asu_redis_1
1:C 04 Jun 2023 19:20:48.491 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 04 Jun 2023 19:20:48.491 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 04 Jun 2023 19:20:48.491 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 04 Jun 2023 19:20:48.491 * monotonic clock: POSIX clock_gettime
1:M 04 Jun 2023 19:20:48.492 * Running mode=standalone, port=6379.
1:M 04 Jun 2023 19:20:48.492 # Server initialized
1:M 04 Jun 2023 19:20:48.492 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:M 04 Jun 2023 19:20:48.494 * Loading RDB produced by version 7.0.11
1:M 04 Jun 2023 19:20:48.494 * RDB age 69 seconds
1:M 04 Jun 2023 19:20:48.494 * RDB memory usage when created 1.34 Mb
1:M 04 Jun 2023 19:20:48.494 * Done loading RDB, keys loaded: 4, keys expired: 1.
1:M 04 Jun 2023 19:20:48.494 * DB loaded from disk: 0.000 seconds
1:M 04 Jun 2023 19:20:48.494 * Ready to accept connections
podman start -a asu_server_1
[2023-06-04 19:20:49 +0000] [2] [INFO] Starting gunicorn 20.1.0
[2023-06-04 19:20:49 +0000] [2] [INFO] Listening at: http://0.0.0.0:8000 (2)
[2023-06-04 19:20:49 +0000] [2] [INFO] Using worker: sync
[2023-06-04 19:20:49 +0000] [3] [INFO] Booting worker with pid: 3
podman start -a asu_worker_1
19:20:50 Worker rq:worker:71a5df14ce3b47bd9c53f9de245757e6 started with PID 1, version 1.15.0
19:20:50 Subscribing to channel rq:pubsub:71a5df14ce3b47bd9c53f9de245757e6
19:20:50 *** Listening on default...
19:20:50 default: asu.janitor.update({'JSON_PATH': PosixPath('/app/public/json/v1'), 'BRANCHES': {'22.03': {'ena...) (9fc6260a-66aa-4654-9c09-a28ca3c0ad52)
podman start -a asu_worker2_1
19:20:51 Worker rq:worker:2290e7b8c6ca429f92e1a13eb4c94269 started with PID 1, version 1.15.0
19:20:51 Subscribing to channel rq:pubsub:2290e7b8c6ca429f92e1a13eb4c94269
19:20:51 *** Listening on default...Works for me. Could you please try the latest commit and make sure that your containers can actually write to the folder?