3 ms·

There are keys to control when these snap updates will happen, https://snapcraft.io/docs/keeping-snaps-up-to-date https://snapcraft.io/docs/keeping-snaps-up-to

by simosx 6y ago

There are keys to control when these snap updates will happen, https://snapcraft.io/docs/keeping-snaps-up-to-date https://snapcraft.io/docs/keeping-snaps-up-to-date It is immutable systems that help you with reproducibility. There is no actual change between the snapd setup in Ubuntu 18.04 and Ubuntu 20.04. Where do you get info on unreliable docker deployments? It looks to me that the dislike is emotional in nature.

fxtentacle 6y ago
I use chromium and firefox inside the docker with selenium to automate website tests. So them replacing the chrome apt with snap was exactly what broke my deployment.
- simosx 6y ago
  Selenium has standalone images with the browser so that you can use them with Docker. It is too fragile to install yourself all the pieces.
  - fxtentacle 6y ago
    I'm actually quite happy with my Ubuntu 18 based homemade docker image. And lucky for me, 18 still has some years of support ahead of it. It's just that I know that I cannot update it to Ubuntu 20 without snap breaking things for me.
    - simosx 6y ago
      If you ever want to switch, the image is `selenium/standalone-chrome`.
      - fxtentacle 6y ago
        Thanks for the hint :)
L3viathan 6y ago
Can I stop one snap from updating (for example indefinitely), while letting the rest update?
- fxtentacle 6y ago
  What I miss most is the ability to pin a version. For example, not every Firefox plugin is compatible with every Firefox update. Especially not if you have custom-developed plug-ins using private APIs.
- simosx 6y ago
  I could not find a key for that, that is, per-package keys. A dirty workaround would be to get the `.snap` package from the store, then install directly from the local file. $ snap download hello-world Fetching snap "hello-world" Fetching assertions for "hello-world" Install the snap with: snap ack hello-world_29.assert snap install hello-world_29.snap $ snap install hello-world_29.snap --dangerous hello-world 6.4 installed $ hello-world Hello World! $ No updates.
cpascal 6y ago
From the linked documentation: > > There are four system-wide options that manage how updates are handed: > - refresh.timer: defines the refresh frequency and schedule > - refresh.hold: delays the next refresh until the defined time and date > - refresh.metered: pauses refresh updates when network connection is metered > - refresh.retain: sets how many revisions of a snap are stored on the system" > I think people would be much happier with snap if there was a `refresh.off` option. If that's too over-the-line for Canonical, a `refresh.prompt` with a dismissible nag-message would be better.
marcinzm 6y ago
>There are keys to control when these snap updates will happen There is no option to permanently disable auto-updates which is the problem being discussed. If I install a docker image with version A and it auto-updates tomorrow to version B then the docker container is no longer reproducible.
amaccuish 6y ago
> It looks to me that the dislike is emotional in nature. But people seem to like flatpaks, so I don't think it's emotional. More a poor implementation.

by simosx 6y ago

fxtentacle 6y ago

I use chromium and firefox inside the docker with selenium to automate website tests. So them replacing the chrome apt with snap was exactly what broke my deployment.

simosx 6y ago
Selenium has standalone images with the browser so that you can use them with Docker. It is too fragile to install yourself all the pieces.
- fxtentacle 6y ago
  I'm actually quite happy with my Ubuntu 18 based homemade docker image. And lucky for me, 18 still has some years of support ahead of it. It's just that I know that I cannot update it to Ubuntu 20 without snap breaking things for me.
  - simosx 6y ago
    If you ever want to switch, the image is `selenium/standalone-chrome`.
    - fxtentacle 6y ago
      Thanks for the hint :)

L3viathan 6y ago

Can I stop one snap from updating (for example indefinitely), while letting the rest update?

fxtentacle 6y ago
What I miss most is the ability to pin a version. For example, not every Firefox plugin is compatible with every Firefox update. Especially not if you have custom-developed plug-ins using private APIs.
simosx 6y ago
I could not find a key for that, that is, per-package keys. A dirty workaround would be to get the `.snap` package from the store, then install directly from the local file. $ snap download hello-world Fetching snap "hello-world" Fetching assertions for "hello-world" Install the snap with: snap ack hello-world_29.assert snap install hello-world_29.snap $ snap install hello-world_29.snap --dangerous hello-world 6.4 installed $ hello-world Hello World! $ No updates.

cpascal 6y ago

From the linked documentation: > > There are four system-wide options that manage how updates are handed: > - refresh.timer: defines the refresh frequency and schedule > - refresh.hold: delays the next refresh until the defined time and date > - refresh.metered: pauses refresh updates when network connection is metered > - refresh.retain: sets how many revisions of a snap are stored on the system" > I think people would be much happier with snap if there was a `refresh.off` option. If that's too over-the-line for Canonical, a `refresh.prompt` with a dismissible nag-message would be better.

marcinzm 6y ago

>There are keys to control when these snap updates will happen There is no option to permanently disable auto-updates which is the problem being discussed. If I install a docker image with version A and it auto-updates tomorrow to version B then the docker container is no longer reproducible.

amaccuish 6y ago

> It looks to me that the dislike is emotional in nature. But people seem to like flatpaks, so I don't think it's emotional. More a poor implementation.