Wallabag Docker image/container update

[nicosomb]

From @Suncatcher on March 30, 2017 11:22

Issue details

I have several questions regarding this:

1. Does Wallabag image/container updated automatically?
2. If not, how can one update it manually without stopping container?
3. If it's not possible without stopping, what is the general procedure?

Having my (very limited) knowledge of Docker, I treat it following way:
when creating container, Docker pulls the latest image from the Hub, but without recreating container it won't update it by default? Am I right?
As it appears, procedure is quite complicated, and to provide consistent updates some changes should be made to application prior to publishing the image.

Environment

• wallabag version that exhibits the issue: 2.2.2
• How did you install wallabag?: Docker
• Last wallabag version that did not exhibit the issue (if applicable): dunno
• php version: dunno
• OS: AWS AMI Linux 2016.e
• type of hosting (shared or dedicated): AWS EC2 T2 Micro
• which storage system you choose at install (SQLite, MySQL/MariaDB or PostgreSQL): Postgre 9.6.2

Steps to reproduce/test case

Trying to update Wallabag container

Copied from original issue: wallabag/wallabag#3018

[nicosomb]

@Suncatcher do you use this container https://hub.docker.com/r/wallabag/wallabag/ ?

[nicosomb]

From @Suncatcher on March 31, 2017 10:0

Exactly. However, I was said it's only for developers and not for users.

[nicosomb]

No, the image available on Docker Hub is for users.
For developers, you need to use docker-compose.yml in https://github.com/wallabag/wallabag repo.

[nicosomb]

From @Suncatcher on March 31, 2017 10:4

So you, guys, should be more consistent in providing info :)

[nicosomb]

Yes we should.

Do we need to move this issue to wallabag/docker repo?

[nicosomb]

From @Suncatcher on March 31, 2017 11:20

I suppose yes.

[Suncatcher]

Nobody can clarify this question?

[xsteadfastx]

you need do stop and remove the container for upgrading. its possible to work with the container and commiting the changes but i would never do that.

[xsteadfastx]

data and the software should be in seperated containers... and in different volumes so they survive container removing and recreating.

[Kdecherf]

Closing this issue as outdated, the container and its update procedure changed a lot since then