Push 3.2.7 release on docker hub

[matnoublanche]

Hi @ayufan,

Thank you very much for your work !

Is it possible to push the latest release on docker hub please ?

Thank you.

Mathieu

[PintjesB]

+1

[n3roGit]

+1

[jcormier]

+1

…

On Tue, Dec 3, 2024, 4:12 AM BubTec ***@***.***> wrote: +1 — Reply to this email directly, view it on GitHub <#56 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABK2RGPLHA67IN2LTH4EQVT2DVYZPAVCNFSM6AAAAABSZYAYNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJTHE2DQNRQGY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[devzwf]

3.3.0 is out , i think it would better to skip 3.2.7

i was able to build the docker image for 3.2.7 for amd64 but have some issue with arm64v8

@ayufan are you still working on this ?

[LgAltair]

Would be nice to have the 3.3 version i hope you have time =)

[ayufan]

I got back home. Will get to it tomorrow and push 3.2 and 3.3 at the same time. Need to update my devices as well :)

[devzwf]

thanks @ayufan let me know if need any testing
I was able to build on Amd but for some reason arm give me trouble

[ayufan]

• The v3.2.7 is released: https://github.com/ayufan/pve-backup-server-dockerfiles/releases/tag/v3.2.7
• The v3.3.2 is released: https://github.com/ayufan/pve-backup-server-dockerfiles/releases/tag/v3.3.2

Tags are as usual (https://hub.docker.com/r/ayufan/proxmox-backup-server/tags):

• ayufan/proxmox-backup-server:v3.2.7
• ayufan/proxmox-backup-server:v3.3.2

I did smoke tests of both on my arm64/NAS. Once more people confirm it working will bump :latest tag.

[codersaur]

I'm running v3.3.2 on an Oracle Cloud Ampere VM.Standard.A1.Flex instance and it's working great. I've tested the new notifications and push sync functionality and everything seems to be working well. Just need to work out how to change the footer link in the notification emails...

[linux-fertxo]

Running v3.3.2 since 3 days ago. I confirm that all is going smooth and by the numbers 😎

Running on bare metal oldie Celeron N3160 NAS

[matnoublanche]

Hi,

Thank you @ayufan !

Confirming that it works well on 3.3.2.

• The v3.2.7 is released: https://github.com/ayufan/pve-backup-server-dockerfiles/releases/tag/v3.2.7
• The v3.3.2 is released: https://github.com/ayufan/pve-backup-server-dockerfiles/releases/tag/v3.3.2

Tags are as usual (https://hub.docker.com/r/ayufan/proxmox-backup-server/tags):

• ayufan/proxmox-backup-server:v3.2.7
• ayufan/proxmox-backup-server:v3.3.2

I did smoke tests of both on my arm64/NAS. Once more people confirm it working will bump :latest tag.

[LgAltair]

Hey, running on TrueNas in Docker Container running very good no problem with Version 3.3.2

[devzwf]

@ayufan works on Unraid ... 3.3.2 (did not test 3.2.7)
so far did not found any issue.

[BeckenrandschwimmerTim]

Can confirm for Unraid: 3.3.2 is working great. Thanks for your work !

[idanoo]

Can confirm for Synology: v3.3.2 works well (amd64).

I did have to manually docker run since you can't add --tmpfs in the UI for the /run mount.

[dwyeraidan]

I'm also running v3.3.2 on an Oracle Cloud Ampere VM.Standard.A1.Flex instance - its working great so far.

Thanks for this work

[ctl26481]

Thanks to ayufan for making PBS in containers possible.

Anyone getting similar dmesg or info messages after upgrading to v3.3.2? It's on amd64 with DSM.

These pop up every 3600 seconds(1hr), I tried to run with logging driver set to none in compose yml and disabled cron(in container shell) but they still appear. I noticed AttachStderr and AttachStdout are configured as True wheres they were False in v3.1.2-1, is that the culprit with these messages popping up?

[***] audit: type=1101 audit(1736014621.234:4157): pid=25974 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_permit acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success'
[***] audit: type=1103 audit(1736014621.248:4158): pid=25974 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit,pam_cap acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success'
[***] audit: type=1105 audit(1736014621.260:4159): pid=25974 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_env,pam_env,pam_permit,pam_unix,pam_limits acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success'
[***] audit: type=1110 audit(1736014621.270:4160): pid=25975 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit,pam_cap acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success'
[***] audit: type=1104 audit(1736014621.277:4161): pid=25974 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success'
[***] audit: type=1106 audit(1736014621.280:4162): pid=25974 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_env,pam_env,pam_permit,pam_unix,pam_limits acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success'

[ayufan]

Oh. Some sort of selinux a like audit logs.

…

On Tue, 7 Jan 2025 at 21:50, ctl26481 ***@***.***> wrote: Thanks to ayufan for making PBS in containers possible. Anyone getting similar dmesg or info messages after upgrading to v3.3.2? It's on amd64 with DSM. These pop up every 3600 seconds(1hr), I tried to run with logging driver set to none in compose yml and disabled cron(in container shell) but they still appear. I noticed AttachStderr and AttachStdout are configured as True wheres they were False in v3.1.2-1, is that the culprit with these messages popping up? [***] audit: type=1101 audit(1736014621.234:4157): pid=25974 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_permit acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success' [***] audit: type=1103 audit(1736014621.248:4158): pid=25974 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit,pam_cap acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success' [***] audit: type=1105 audit(1736014621.260:4159): pid=25974 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_env,pam_env,pam_permit,pam_unix,pam_limits acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success' [***] audit: type=1110 audit(1736014621.270:4160): pid=25975 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit,pam_cap acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success' [***] audit: type=1104 audit(1736014621.277:4161): pid=25974 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success' [***] audit: type=1106 audit(1736014621.280:4162): pid=25974 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_env,pam_env,pam_permit,pam_unix,pam_limits acct="root" exe="/usr/sbin/cron" hostname=? addr=? terminal=cron res=success' — Reply to this email directly, view it on GitHub <#56 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AASOSQNUYKBOHFNGHYF42AD2JQ43DAVCNFSM6AAAAABSZYAYNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZWGE4TMMBSGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>