Kann Image nicht starten
Hi hi,
ich hatte den Docker bis vor kurzem auf Manjaro laufen, bis Manjaro nicht mehr wollte. Nun hab ich spontan Ubuntu installiert und das alte Home in Ubuntu eingebunden.
Also in Ubuntu 21.10 docker installiert und das Image eingebunden, es wird auch gesehen, aber beim starten kommen Fehlermeldungen.
reiner@reiner-desktop:~$ sudo docker run abaa6ea0f560
[sudo] Passwort für reiner:
Paperless-ng docker container starting...
Creating directory ../data/index
Creating directory ../media/documents
Creating directory ../media/documents/originals
Creating directory ../media/documents/thumbnails
Creating directory /tmp/paperless
Adjusting permissions of paperless files. This may take a while.
Apply database migrations...
Operations to perform:
Apply all migrations: admin, auth, authtoken, contenttypes, django_q, documents, paperless_mail, sessions
Running migrations:
Applying contenttypes.0001_initial... OK
Applying auth.0001_initial... OK
Applying admin.0001_initial... OK
Applying admin.0002_logentry_remove_auto_add... OK
Applying admin.0003_logentry_add_action_flag_choices... OK
Applying contenttypes.0002_remove_content_type_name... OK
Applying auth.0002_alter_permission_name_max_length... OK
Applying auth.0003_alter_user_email_max_length... OK
Applying auth.0004_alter_user_username_opts... OK
Applying auth.0005_alter_user_last_login_null... OK
Applying auth.0006_require_contenttypes_0002... OK
Applying auth.0007_alter_validators_add_error_messages... OK
Applying auth.0008_alter_user_username_max_length... OK
Applying auth.0009_alter_user_last_name_max_length... OK
Applying auth.0010_alter_group_name_max_length... OK
Applying auth.0011_update_proxy_permissions... OK
Applying auth.0012_alter_user_first_name_max_length... OK
Applying authtoken.0001_initial... OK
Applying authtoken.0002_auto_20160226_1747... OK
Applying authtoken.0003_tokenproxy... OK
Applying django_q.0001_initial... OK
Applying django_q.0002_auto_20150630_1624... OK
Applying django_q.0003_auto_20150708_1326... OK
Applying django_q.0004_auto_20150710_1043... OK
Applying django_q.0005_auto_20150718_1506... OK
Applying django_q.0006_auto_20150805_1817... OK
Applying django_q.0007_ormq... OK
Applying django_q.0008_auto_20160224_1026... OK
Applying django_q.0009_auto_20171009_0915... OK
Applying django_q.0010_auto_20200610_0856... OK
Applying django_q.0011_auto_20200628_1055... OK
Applying django_q.0012_auto_20200702_1608... OK
Applying django_q.0013_task_attempt_count... OK
Applying django_q.0014_schedule_cluster... OK
Applying documents.0001_initial... OK
Applying documents.0002_auto_20151226_1316... OK
Applying documents.0003_sender... OK
Applying documents.0004_auto_20160114_1844... OK
Applying documents.0005_auto_20160123_0313... OK
Applying documents.0006_auto_20160123_0430... OK
Applying documents.0007_auto_20160126_2114... OK
Applying documents.0008_document_file_type... OK
Applying documents.0009_auto_20160214_0040... OK
Applying documents.0010_log... OK
Applying documents.0011_auto_20160303_1929... OK
Applying documents.0012_auto_20160305_0040... OK
Applying documents.0013_auto_20160325_2111... OK
Applying documents.0014_document_checksum... OK
Applying documents.0015_add_insensitive_to_match... OK
Applying documents.0016_auto_20170325_1558... OK
Applying documents.0017_auto_20170512_0507... OK
Applying documents.0018_auto_20170715_1712... OK
Applying documents.0019_add_consumer_user... OK
Applying documents.0020_document_added... OK
Applying documents.0021_document_storage_type... OK
Applying documents.0022_auto_20181007_1420... OK
Applying documents.0023_document_current_filename... OK
Applying documents.1000_update_paperless_all... OK
Applying documents.1001_auto_20201109_1636... OK
Applying documents.1002_auto_20201111_1105... OK
Applying documents.1003_mime_types... OK
Applying documents.1004_sanity_check_schedule... OK
Applying documents.1005_checksums... OK
Applying documents.1006_auto_20201208_2209... OK
Applying documents.1007_savedview_savedviewfilterrule... OK
Applying documents.1008_auto_20201216_1736... OK
Applying documents.1009_auto_20201216_2005... OK
Applying documents.1010_auto_20210101_2159... OK
Applying documents.1011_auto_20210101_2340... OK
Applying documents.1012_fix_archive_files... OK
Applying documents.1013_migrate_tag_colour... OK
Applying documents.1014_auto_20210228_1614... OK
Applying documents.1015_remove_null_characters... OK
Applying documents.1016_auto_20210317_1351... OK
Applying paperless_mail.0001_initial... OK
Applying paperless_mail.0002_auto_20201117_1334... OK
Applying paperless_mail.0003_auto_20201118_1940... OK
Applying paperless_mail.0004_mailrule_order... OK
Applying paperless_mail.0005_help_texts... OK
Applying paperless_mail.0006_auto_20210101_2340... OK
Applying paperless_mail.0007_auto_20210106_0138... OK
Applying paperless_mail.0008_auto_20210516_0940... OK
Applying sessions.0001_initial... OK
Search index out of date. Updating...
0it [00:00, ?it/s]
Executing /usr/local/bin/supervisord -c /etc/supervisord.conf
2022-03-17 10:22:30,401 INFO Set uid to user 0 succeeded
2022-03-17 10:22:30,403 INFO supervisord started with pid 1
2022-03-17 10:22:31,406 INFO spawned: 'consumer' with pid 48
2022-03-17 10:22:31,407 INFO spawned: 'gunicorn' with pid 49
2022-03-17 10:22:31,409 INFO spawned: 'scheduler' with pid 50
[2022-03-17 10:22:31 +0000] [49] [INFO] Starting gunicorn 20.1.0
[2022-03-17 10:22:31 +0000] [49] [INFO] Listening at: http://0.0.0.0:8000 (49)
[2022-03-17 10:22:31 +0000] [49] [INFO] Using worker: paperless.workers.ConfigurableWorker
[2022-03-17 10:22:31 +0000] [49] [INFO] Server is ready. Spawning workers
[2022-03-17 10:22:32,285] [INFO] [paperless.management.consumer] Using inotify to watch directory for changes: /usr/src/paperless/src/../consume
10:22:32 [Q] INFO Q Cluster lactose-oven-vermont-sink starting.
10:22:32 [Q] ERROR Can not connect to Redis server.
Process Process-1:
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/redis/connection.py", line 559, in connect
sock = self._connect()
File "/usr/local/lib/python3.9/site-packages/redis/connection.py", line 615, in _connect
raise err
File "/usr/local/lib/python3.9/site-packages/redis/connection.py", line 603, in _connect
sock.connect(socket_address)
OSError: [Errno 99] Cannot assign requested addressDuring handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.9/multiprocessing/process.py", line 315, in _bootstrap
self.run()
File "/usr/local/lib/python3.9/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/usr/local/lib/python3.9/site-packages/django_q/cluster.py", line 168, in __init__
self.start()
File "/usr/local/lib/python3.9/site-packages/django_q/cluster.py", line 171, in start
self.broker.ping()
File "/usr/local/lib/python3.9/site-packages/django_q/brokers/redis_broker.py", line 39, in ping
raise e
File "/usr/local/lib/python3.9/site-packages/django_q/brokers/redis_broker.py", line 36, in ping
return self.connection.ping()
File "/usr/local/lib/python3.9/site-packages/redis/client.py", line 1378, in ping
return self.execute_command('PING')
File "/usr/local/lib/python3.9/site-packages/redis/client.py", line 898, in execute_command
conn = self.connection or pool.get_connection(command_name, **options)
File "/usr/local/lib/python3.9/site-packages/redis/connection.py", line 1192, in get_connection
connection.connect()
File "/usr/local/lib/python3.9/site-packages/redis/connection.py", line 563, in connect
raise ConnectionError(self._error_message(e))
redis.exceptions.ConnectionError: Error 99 connecting to localhost:6379. Cannot assign requested address.
2022-03-17 10:22:33,378 INFO success: consumer entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-03-17 10:22:33,378 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-03-17 10:22:33,378 INFO success: scheduler entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
nun habe ich noch was redis gespielt
sudo redis-server /etc/redis/redis.conf
das klappt, aber
docker run --name abaa6ea0f560 -d redis
docker: Error response from daemon: Conflict. The container name "/abaa6ea0f560" is already in use by container "d029ca576a8675fdd85d4ce218cfe3112d59ba17abfde9a3d396d7cf5c66a74f". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.
bzw.
docker run --name jonaswinkler/paperless-ng -d redis
docker: Error response from daemon: Invalid container name (jonaswinkler/paperless-ng), only [a-zA-Z0-9][a-zA-Z0-9_.-] are allowed.
See 'docker run --help'.
das nicht. Nun hab ich den Contain umbenannt, ohne Erfolg.
docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
postgres 13 77365f9e496c 8 days ago 373MB
redis 6.0 67208ce263c6 13 days ago 112MB
redis latest 0e403e3816e8 13 days ago 113MB
jonaswinkler/paperless-ng latest abaa6ea0f560 6 months ago 1.09GB
10:22:32 [Q] ERROR Can not connect to Redis server.
OSError: [Errno 99] Cannot assign requested address
Es könnte daran liegen, dass die Angesprochene IP Adresse an keines der Interface gebunden ist. Wenn ich das richtig verstanden habe, hast du einfach die Daten von deinem alten Manjaro System rüber kopiert und jetzt wieder starten wollen, sehe ich das richtig?
Hi
damit geht eine Intakte DB
docker-compose up -d
aus dem Paperless Ordner
Das alte Image macht immer noch Probleme
docker-compose up -d
ERROR: yaml.scanner.ScannerError: mapping values are not allowed here
in "./docker-compose.yml", line 66, column 23
65 PAPERLESS_REDIS: redis://broker:6379
66 PAPERLESS_DBHOST: db