Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Failing to pull images tagged with 0.3 #351

Closed
brianemwd opened this issue Nov 21, 2019 · 16 comments
Closed

[BUG] Failing to pull images tagged with 0.3 #351

brianemwd opened this issue Nov 21, 2019 · 16 comments
Labels

Comments

@brianemwd
Copy link
Contributor

My understanding is that Mailman 3.3 was now available via docker. However I am getting the following error when testing this out:

docker pull maxking/mailman-core:0.3.0
Error response from daemon: manifest for maxking/mailman-core:0.3.0 not found: manifest unknown: manifest unknown

Please advise. Thanks!

@brianemwd brianemwd added the bug label Nov 21, 2019
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.85. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@maxking
Copy link
Owner

maxking commented Nov 21, 2019 via email

@brianemwd
Copy link
Contributor Author

I did try the 0.3 tag and I received the same error message.

@brianemwd
Copy link
Contributor Author

Actually the error message is different:

docker pull maxking/mailman-core:0.3
Error response from daemon: mediaType in manifest should be 'application/vnd.docker.distribution.manifest.v2+json' not ''

@maxking
Copy link
Owner

maxking commented Nov 24, 2019

What version of docker are you using?

@maxking maxking changed the title [BUG] [BUG] Failing to pull images tagged with 0.3 Nov 24, 2019
@brianemwd
Copy link
Contributor Author

Docker version 19.03.4

@maxking
Copy link
Owner

maxking commented Nov 25, 2019

Can you retry once? Perhaps from a different machine?

╰─$ docker pull maxking/mailman-core:0.3
0.3: Pulling from maxking/mailman-core
a02ede7c9785: Pull complete 
1dbcab28ce46: Pull complete 
e9f61ec01614: Pull complete 
4832a7d92cf4: Pull complete 
Digest: sha256:ae136dcc5d830d0c596513aae56a2fa611f02110068d2d221faf6982fceb8eeb
Status: Downloaded newer image for maxking/mailman-core:0.3
docker.io/maxking/mailman-core:0.3
╭─maxking@workvm ~ 
╰─$ docker --version                    
Docker version 19.03.5, build 633a0ea838

@brianemwd
Copy link
Contributor Author

This seems to be the same issues as listed at:

docker/hub-feedback#1871

@maxking
Copy link
Owner

maxking commented Nov 27, 2019

Try out if this works for you: docker pull maxking/mailman-core:0.3.0

I made sure that this gets built on the docker hub, so it doesn't encounter the bug which seems to be related to using podman.

Note the 0.3.0 is the tag. Should work for mailman-web too.

@brianemwd
Copy link
Contributor Author

That worked but Postorius is still at version 1.2.4 and Hyperkitty at 1.2.2. I don't that is correct.

@maxking
Copy link
Owner

maxking commented Nov 27, 2019

Did you recreate the container? I tested it out and the image seems to have the latest versions.

$ docker run -e SECRET_KEY=som -it maxking/mailman-web:0.3.0 bash
DATABASE_URL is not defined. Using sqlite database...
Creating log file for mailman web
Creating log file for uwsgi..
settings_local.py not found, it is highly recommended that you provide one
Using default configuration to run.

369 static files copied to '/opt/mailman-web-data/static'.
Operations to perform:
  Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, openid, postorius, sessions, sites, socialaccount
Running migrations:
  Applying contenttypes.0001_initial... OK
  Applying auth.0001_initial... OK
  Applying account.0001_initial... OK
  Applying account.0002_email_max_length... 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 sites.0001_initial... OK
  Applying django_mailman3.0001_initial... OK
  Applying django_mailman3.0002_maildomain... 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 socialaccount.0001_initial... OK
  Applying socialaccount.0002_token_max_lengths... OK
  Applying socialaccount.0003_extra_data_default_dict... OK
  Applying hyperkitty.0001_initial... OK
  Applying hyperkitty.0002_auto_20150311_0913... OK
  Applying hyperkitty.0003_thread_starting_email... OK
  Applying hyperkitty.0004_archived_date_and_subject... OK
  Applying hyperkitty.0005_MailingList_list_id... OK
  Applying hyperkitty.0006_thread_on_delete... OK
  Applying hyperkitty.0007_allauth_20160808_1604... OK
  Applying hyperkitty.0008_django_mailman3_profile... OK
  Applying hyperkitty.0009_duplicate_persona_users... OK
  Applying hyperkitty.0010_email_sender_name... OK
  Applying hyperkitty.0011_email_parent... OK
  Applying hyperkitty.0012_thread_order_null... OK
  Applying hyperkitty.0013_mailinglist_id_1... OK
  Applying hyperkitty.0014_mailinglist_id_2... OK
  Applying hyperkitty.0015_mailinglist_id_3... OK
  Applying hyperkitty.0016_auto_20180309_0056... OK
  Applying hyperkitty.0017_file_attachments... OK
  Applying hyperkitty.0018_threadcategory_color... OK
  Applying hyperkitty.0019_auto_20190127_null_description... OK
  Applying openid.0001_initial... OK
  Applying postorius.0001_initial... OK
  Applying postorius.0002_auto_20160210_0721... OK
  Applying postorius.0003_drop_addressconfirmationprofile... OK
  Applying postorius.0004_create_email_template... OK
  Applying postorius.0005_auto_20180707_1107... OK
  Applying postorius.0006_auto_20180711_1359... OK
  Applying postorius.0007_auto_20180712_0536... OK
  Applying postorius.0008_auto_20190310_0717... OK
  Applying postorius.0009_auto_20190508_1604... OK
  Applying sessions.0001_initial... OK
  Applying sites.0002_alter_domain_unique... OK
bash-4.4# pip list
Package             Version  
------------------- ---------
arrow               0.15.4   
atpublic            1.0      
bleach              3.1.0    
blessed             1.16.1   
certifi             2019.9.11
cffi                1.13.2   
chardet             3.0.4    
cmarkgfm            0.4.2    
decorator           4.4.1    
defusedxml          0.6.0    
dj-database-url     0.5.0    
Django              2.2      
django-allauth      0.40.0   
django-appconf      1.0.3    
django-compressor   2.3      
django-extensions   2.2.5    
django-gravatar2    1.4.2    
django-haystack     2.8.1    
django-mailman3     1.3.0    
django-picklefield  2.0      
django-q            1.0.2    
djangorestframework 3.10.3   
docutils            0.15.2   
flufl.lock          3.2      
HyperKitty          1.3.0    
idna                2.8      
mailmanclient       3.3.0    
mysqlclient         1.4.6    
networkx            2.4      
oauthlib            3.1.0    
pip                 19.3.1   
postorius           1.3.0    
psycopg2            2.8.4    
pycparser           2.19     
Pygments            2.4.2    
python-dateutil     2.8.1    
python3-openid      3.1.0    
pytz                2019.3   
rcssmin             1.0.6    
readme-renderer     24.0     
requests            2.22.0   
requests-oauthlib   1.3.0    
rjsmin              1.1.0    
robot-detection     0.4      
setuptools          40.6.2   
six                 1.13.0   
sqlparse            0.3.0    
typing              3.7.4.1  
urllib3             1.25.7   
uWSGI               2.0.18   
wcwidth             0.1.7    
webencodings        0.5.1    
Whoosh              2.7.4    
xapian-haystack     2.1.1    
bash-4.4# 

@brianemwd
Copy link
Contributor Author

I did not know about the recreate container part however I did that and still running Postorius 2.4 and HK 2.2. Here were my steps:

$ docker-compose stop
$ docker-compose rm
$ docker pull maxking/mailman-core:0.3.0
$ docker pull maxking/mailman-web:0.3.0
$docker run -e SECRET_KEY=somesecretkey -it maxking/mailman-web:0.3.0 bash
$bash exit
$ docker-compose up -d

I got the exact output you showed above but I am still running the older versions.

@brianemwd
Copy link
Contributor Author

I also tried running:

docker-compose up -d --force-recreate

Still same versions.

@brianemwd
Copy link
Contributor Author

docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
352be266f59f maxking/mailman-web:0.3.0 "docker-entrypoint.s…" 6 minutes ago Exited (0) 6 minutes ago vigorous_rubin
c63320d2d22f maxking/mailman-web:0.2 "docker-entrypoint.s…" 12 minutes ago Up 12 minutes 8000/tcp, 8080/tcp mailman-web
bf9a67829625 maxking/mailman-core:0.2 "docker-entrypoint.s…" 12 minutes ago Up 12 minutes 8001/tcp, 8024/tcp mailman-core
12bf3432ef1f postgres:9.6-alpine "docker-entrypoint.s…" 12 minutes ago Up 12 minutes 5432/tcp docker-mailman_database_1_98e5452d4fcc
9ce7d07e7a53 maxking/mailman-web:0.3.0 "docker-entrypoint.s…" 46 minutes ago Exited (0) 45 minutes ago compassionate_williamson
ad91af562eb5 maxking/mailman-web:0.3.0 "docker-entrypoint.s…" 51 minutes ago Exited (130) 51 minutes ago gifted_rubin
10a31a43c672 hello-world "/hello" 11 months ago Exited (0) 11 months ago wonderful_khorana

@brianemwd
Copy link
Contributor Author

brianemwd commented Nov 28, 2019

I figured out the problem. I forgot to update the docker-compose.yaml file to use the new containers. I still blame maxking. :^)

@maxking
Copy link
Owner

maxking commented Nov 28, 2019

Glad that you got it figured it out, I did realize that could have been the problem but only after you figured it out yourself :)

@maxking maxking closed this as completed Nov 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants